Related
I guess this is my honeycomb ignorance (still getting used to the features) but when pulling up recent apps with the softkey I really only want apps that are currently running.
Are some of these apps are already "closed" and by choosing a thumbnail from the list I'm re-opening these?
Is there a setting anywhere to "limit" the history I see? Like <5 apps or something?
I have Task Killer pro intalled now to manage the real running apps but the Softkey is handier, if I can just be sure of what its supposed to indicate.
Thanks
Sent from my Transformer TF101 using XDA Premium App
I was wondering this as well. I haven't found any way to do it yet.
I don't know of any way except to manage apps in the settings and then kill "running" apps....but remember; these are apps "in memory" like you'd think in Windows.....they are not sucking resources...
I think that there is an article here somewhere about this list and why you shouldn't use an app killer in Honeycomb....
I'm more interested in changing it to a grid layout, like a speed dial.
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
moo99 said:
yeah I know theyre not in memory but they are wasting screen space. I finished playing chess yesterday, I dont think the game should stay in the recent apps list. Froyo & Gingerbread are much better at managing this.
Click to expand...
Click to collapse
I agree. I just want a cleaner recent apps list. Sometimes it's hard to find what you're looking for.
I guess a workaround would be to longpress the home screen, put a widget there that is linked directly to "manage applications" and then it would only be one press and then zap the offending apps.
You do realize the Recent Apps button on the homescreen is just that, a Recent Apps button. It's not exactly a "running in the background" button.
"I finished playing chess yesterday, I dont think the game should stay in the recent apps list."
Why not? It is a recently played app isn't it? LOL.
And yeah, agree with the other reply, if you want a list of running apps.... don't touch the Recent Apps list button lol.
Stop worrying about what's running in the background. Just enjoy the damn Android.
Im not near my TF now but I use Multitasking Pro on my Galaxy S for that. you can choose to open it by double clicking the home button and see only running apps or recent apps - its configurable in the application settings. i does cost about 2$ i think but it was the best 2$ I've spent
this is called a 'Recent apps' list for a reason...it's 'Recent'..not current running...
Well you could always downgrade to 3.0 if it really bothers you. That only showed 5 apps!
LOL. Its a nuisance, not so much a grievance; but I'm glad I'm not the only one annoyed, perhaps this will get looked at ;-)
Possibly once Honeycomb is more prevalent there will come market apps or enough reportage to have an updte with a setting for it, or a utility that tweaks it. Regardless, I appreciate the feedback. At least now I know its sort of "normal".
Sent from my Transformer TF101 using XDA Premium App
My number one wish is for Google to improve multitasking (and give back control to the user as to which programs are running).
As is, the implementation just isn't very usable if you consider it to be a multitasking device -- it's really closer to single-tasking with a memory of what it did recently and the ability to reopen with a similar state to what it last had.
For example, I use my tab during F1 races for timing and scoring. I have F1.com's timing and scoring app, and I have access to a (non-public) website which provides further real-time info through Adobe Flash in a web browser.
If I switch from the web browser to F1.com's timing and scoring app for more than say 10-15 seconds, then back again, the flash app has to reconnect to the server because the web browser ceased running, even though the browser and the F1.com app were the only programs running and had ample memory / CPU power / a mains power supply connected, ie. no reason to halt the browser.
This isn't the only time I hit this issue, it's just one easy-to-explain example.
I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
knoxploration said:
.I'd much rather I had the ability to exit programs / apps myself when I'm done with them, and to keep programs / apps running in the background when I want them to. It'd make the whole experience much more coherent and logical.
Click to expand...
Click to collapse
The problem is that the vast majority of users won't want to handle this themselves, and would expect the OS to do if for them.
Personally, I'm in favour of having some sort of mechanism whereby you can tell the OS not to kill specific tasks if you so choose, but otherwise task management performs as is.
With specific regard to your example, I think that the OS believes it is always OK to kill the browser, which is why it can be killed so quickly after switching away. For other apps, this doesn't seem to happen - for example, yesterday I was connected to a remote server using Wyse PocketCloud, and I frequently switched away to do something else for 30-60 minutes at a time, yet my remote desktop connection was never dropped or killed.
Regards,
Dave
Me personally don't need and don't like this "recent" app button. Or I need it to have an option either to clear it or not. You know we sometimes need privacy over such things
JCopernicus said:
The Flash plugin was designed to suspend when you switched apps. It's not an android issue.
Adding "close programs" to the current implementation would not make it more logical, it would make it more convoluted. It doesn't need it.
Click to expand...
Click to collapse
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
...and it should be *my* choice whether that happens. That is where this argument totaly falls on its face. *I* know whether it is vital to me that an app remain open, or can safely be closed. The tablet doesn't.
As long as it remains in the tablet's hands, it will continue to annoy me by leving open apps that I no longer need running, while closing apps that I strongly do need running.
magicpork said:
Agreed, if flash is left to run in the background it will drain the battery like hell..and other system resources as well.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
that's just it....it doesn't.
Revisiting Android Task Killers and Why You Still Don’t Need One
from another forum.
We almost hate to approach the topic of Task Killers on Android after all this time, but with so many new faces here at Droid Life and in Android in general, it’s something that needs to be done. In fact, after seeing the Amazon app of the day and reading through the Twitter conversations we just had with many of you, this thing needs to be posted immediately.
Let’s see if we can’t get you all some better battery life!
First off, please ignore the image up at the top of the post. If this was 2009 and we were all running something less than Android 2.2, that statement plastered on that red banner might be somewhat correct. But since it is 2011 and the majority of people on the planet are running Android 2.2, we need to get you away from the mindset that killing off tasks on your phone is a good thing.
So rather than me blabbering about the inner-workings of Android and how it manages RAM for the 10,000th time, I’m going to just pull from some posts that friends of ours have done that explain this in the plainest of ways.
First up is our boy @cvpcs who you may know from CM and his Sapphire ROM days. He knows Android inside-and-out, so when he goes into memory management which is done by the OS itself, you should listen up:
…What people don’t seem to realize is that android is designed to have a large number of tasks stored in memory at all times. Why? Well basically we are talking about a mobile device. On a mobile device things tend to be slower. The hardware isn’t as robust as say a desktop or a laptop, so in order to get that same “snappy” feeling, there have to be workarounds.
One of these is how android deals with memory. Android will load up your apps and then keep them running until they absolutely HAVE to kill them. This is because that way, if you want to re-open an app, the system already has it loaded and can then just resume it instead of reloading it. This provides a significant performance increase.
What a lot of people don’t realize as well is that android kernels have their own task manager. This means that:
it will be more efficient than any app-based task manager as it is run at the kernel level, and
it should be left up to that task killer to decide when to free up memory
There is only one case where having a task killer is a good idea, and that is when you want to kill ONE SPECIFIC APP. Killing all apps is never a good idea. You don’t know what operations they are performing or if they are necessary.
Whitson Gordon of Lifehacker suggests that you should be more worried about CPU usage than what’s going on with your RAM. We agree:
This set-up implies that the goal of killing these apps is to free up memory. Nowhere on the list does it mention the number of CPU cycles each app is consuming, only the memory you’ll free by killing it. As we’ve learned, full memory is not a bad thing—we want to watch out for the CPU, the resource that actually slows down your phone and drains your battery life.
Thus, killing all but the essential apps (or telling Android to kill apps more aggressively with the “autokill” feature) is generally unnecessary. Furthermore, it’s actually possible that this will worsen your phone’s performance and battery life. Whether you’re manually killing apps all the time or telling the task killer to aggressively remove apps from your memory, you’re actually using CPU cycles when you otherwise wouldn’t—killing apps that aren’t doing anything in the first place.
In fact, some of the processes related to those apps will actually start right back up, further draining your CPU. If they don’t, killing those processes can cause other sorts of problems—alarms don’t go off, you don’t receive text messages, or other related apps may force close without warning. All in all, you’re usually better off letting your phone work as intended—especially if you’re more of a casual user. In these instances, a task killer causes more problems than it solves.
More on how Android has a built-in memory-management system, but also on how killing all tasks is not a good thing (via: NextApp):
Android was designed from the ground up as an operating system (OS) for mobile devices. Its built-in application and memory-management systems were engineered with battery life as one of the most critical concerns.
The Android OS does not work like a desktop operating system. On a desktop OS, like Windows, Mac OS X, or Ubuntu Linux, the user is responsible for closing programs in order to keep a reasonable amount of memory available. On Android, this is not the case. The OS itself automatically removes programs from memory as memory is needed. The OS may also preload applications into memory which it thinks might soon be needed.
Having lots of available empty memory is not a good thing. It takes the same amount of power to hold “nothing” in memory as it does to hold actual data. So, like every other operating system in use today, Android does its best to keep as much important/likely-to-be-used information in memory as possible.
As such, using the task manager feature of SystemPanel to constantly clear memory by killing all apps is strongly NOT RECOMMENDED. This also applies to any other task killer / management program. Generally speaking, you should only “End” applications if you see one which is not working correctly. The “End All” feature can be used if your phone/device is performing poorly and you are uncertain of the cause.
And we could go on for hours with source after source on why task killers do nothing but work against Android, but you probably get the point now don’t you? Ready for a quick recap? OK.
Basically, Android keeps tasks handy because it thinks you’ll want to perform them again in a very short amount of time. If you don’t, it will clear them out for you. It also likes to keep as many things handy as possible so that the overall performance of your device is top notch. If Android were to completely kill off everything that your phone is doing, then it would require more resources to restart all of them and you would likely run into slowness and battery drains. By keeping certain things available to you, your phone is actually running better than it would without. So please, stop killing off tasks and let Android do the work for you.
Your goal for the week is wash your brain of the idea that having little RAM available is a bad thing. The more RAM available, the more Android will find ways to use it up which means your battery will be dead in hours. Instead, let it manage itself, so that you can spend more time playing Angry Birds or reading Droid Life.
All good now?
A simple reboot clears the list of recent apps. And as others have stated, it's not about running apps but something like the "recent documents" list in Windows 7
This is my 4th Android phone, and I am still a little unclear on how memory works on this machine. I use AutoKiller, yet I am still confused. As I understand it, 100mb or 5mb free, it shouldn't affect the operation of the device until something needs more than the available and has to clear room. So, how does this work, exactly? I am continually running low on the Triumph, yet if I set the preset in AutoKiller higher, I begin to lose services ranging from alarm clocks to social networking notifications. Where do I begin to find balance? Am I missing something?
I haven't had a problem with starting to lose services like the alarm clock but I was seeing the system significantly slow down even as I kept all unnecessary tasks from running. So I figured that I would root my system, and get rid of all the pre-installed software that I didn't use. The funny thing is that after I rooted the system all the memory issues went away, and the system really flies now. I don't know what changed, when I rooted it. But I am not seeing the same slow responses, the constant starting of tasks that I don't use and so forth. I know that its not an answer so to say, but I thought that I would share so as to maybe help you, or see if it happened with someone else.
HitchHiker said:
I haven't had a problem with starting to lose services like the alarm clock but I was seeing the system significantly slow down even as I kept all unnecessary tasks from running. So I figured that I would root my system, and get rid of all the pre-installed software that I didn't use. The funny thing is that after I rooted the system all the memory issues went away, and the system really flies now. I don't know what changed, when I rooted it. But I am not seeing the same slow responses, the constant starting of tasks that I don't use and so forth. I know that its not an answer so to say, but I thought that I would share so as to maybe help you, or see if it happened with someone else.
Click to expand...
Click to collapse
Thanks for the reply. It's nice to hear other experiences. I am already rooted, and AutoKiller requires root. I'm just being patient and hoping that a custom ROM can solve problems.
Rooting shouldn't change anything except whether or not the phone is rooted. That's it. Task killers rarely help because those apps you kill just come back as soon as you look away. So I would personally recommend you only kill the miscreant apps, and ultimately remove them if you can.
Sent from my Frankenphone using Tapatalk
primetechv2 said:
Rooting shouldn't change anything except whether or not the phone is rooted. That's it. Task killers rarely help because those apps you kill just come back as soon as you look away. So I would personally recommend you only kill the miscreant apps, and ultimately remove them if you can.
Sent from my Frankenphone using Tapatalk
Click to expand...
Click to collapse
Autokiller doesn't work that way. It merely changes Android's already existing internal programming to be a touch more aggressive. It does nothing on its own, merely giving you an interface to alter Android's own values for task management and app priority.
What I really need to know is if that aggression is necessary. Android's default minimum for memory is 24mb (that is the level at which the system will kill off empty apps). I can raise that number, but is it necessary? Some one told me that free memory amount is irrelevant in Android. If that's true, what is the point in making sure my system has 100mb free as opposed to 20mb?
I wouldn't think that extra memory management app is necessary, the only problems any android 2.2 phone (or any android) has are apps that are coded porely are installed. Just use a app that shows cpu usage. If a app is porely written you will see it..... those are the ones to uninstall.....not kill, uninstall.
tsac said:
I wouldn't think that extra memory management app is necessary, the only problems any android 2.2 phone (or any android) has are apps that are coded porely are installed. Just use a app that shows cpu usage. If a app is porely written you will see it..... those are the ones to uninstall.....not kill, uninstall.
Click to expand...
Click to collapse
Like I said, the app merely gives me a UI to alter Android's already existing internal programming in regards to service priority. I am just trying to better understand how Android does it's work.
Hello,
I'm considering purchasing One X but after reading so many posts about multitasking issues I have serious doubts. I can not really check this since it takes time to see the issue but how if I don't use Sense (use alternative launcher like GoLauncher, will I still have this issue or Sense is bigger then just laucher itself.
artisticcheese said:
Hello,
I'm considering purchasing One X but after reading so many posts about multitasking issues I have serious doubts. I can not really check this since it takes time to see the issue but how if I don't use Sense (use alternative launcher like GoLauncher, will I still have this issue or Sense is bigger then just laucher itself.
Click to expand...
Click to collapse
Sense is bigger than the launcher. Sense affects a lot of the core phone's features can can't be removed with just a launcher. In this particular case, Sense affects memory management, as well as the actual multitasking app itself.
Let's put it this way. If you're playing a game like say... Radiant Defense (awesome game, btw) that takes a while to complete a level and you get a text message... switching to the messaging app will actually cause the game to close. Now you can use the "multitasking" app to go back to the game, but the game will reload. It will not leave off where you left it.
If that sounds like something that would bother you a lot... I'd avoid the phone. HTC has even said that this is a core Sense 4 FEATURE, not a defect. So they won't be fixing it.
Personally don't think this really warrants a new thread, you probably should have just asked in the ongoing discussion on this.
Haven't tried an alternate launcher yet, so I can't comment on that. But as to the basic question of "how bad" the issue is, I think it depends greatly on how you use your phone, and what you expect from it. Obviously, HTC expects most people to be okay with it, or they wouldn't have tweaked it this way. Only had the phone for a few days, but so far the memory management doesn't seem much different from how the HTC Flyer does it, and I've been fine with that (having owned it since June 2011).
Like posted above, Sense is more than just a launcher. The multi-task changes are likely deep in the kernel.
To me, it is not a big deal. I don't like anything running in the background anyway. And for that matter, the number 1 app in the past a typical Android user uses is Auto Task killer which serves the exact same purpose as the new Sense 4.0. I suspect a lot of those Auto Tasker kill users now also the ones who complain about HTC's feature.
Either way, the biggest problem is with Android itself. There isn't any uniform way to inform OS that an app requires to remain running in background (unless you created a service) can be kept that way. And there is no way for an app that doesn't do anything in the background to be suspended without using any system resources. For later, both iOS and WP7 have much better implementation.
For many years now, I use Google Listen as my podcast player everyday. It works in most times while in the background but a lot of occasions, this app will be closed by OS while I'm listening to the podcast. This behavior is the same on couple different Android phones (samsung and now HTC One X). So, if google's own app can't even stay alive in background in various Android phones, it speaks volume that multi-tasking is a over-hyped feature. What HTC did is not necessary bad to everyone. For example, my Samsung phones (SGS, SGS2 and GTab 10.1) doesn't auto kill bakcground tasks (still kills my GListen) but they all lags badly from time to time.
For what it worth, I can use Google Listen in the background while running Google Nav app in the fore ground for a few hours without problem (other than occasionally Listen get closed for no reason).
I have had mine for 2 weeks and only knew about a "problem" from reading these threads.
In all in how you use it. First reply answered it best
ricktat said:
I have had mine for 2 weeks and only knew about a "problem" from reading these threads.
In all in how you use it. First reply answered it best
Click to expand...
Click to collapse
Agreed. The only app I use for streaming in the background is subsonic, which functions just fine.
Also I have the very very slight annoyance that games have to completely reload if you exit them and don't switch back very very quickly. So if I get a phone call and go right back to game it's fine, but if I go web browse or something else and go back the game has to reload. This is mitigated somewhat by the raw speed of the phone, as game loading doesn't take very long (unless the game is a ****ty port like PvZ).
To avoid confusion, lets just keep this conversation with the ongoing one here. Thanks.
Thread closed.
This is my first post on XDA and although i'm not new to the android scene having owned a lot of devices in previous years but I never came down to post queries of my own cause everything used to go real smooth!
I recently got a Nexus S i9020t from a friend and tried flashing a Jelly Bean rom on my device.
No issues so far with everything working with every rom that i've tried...
The only thing that bugs me is the ram.
I've tried several kernels on top of different roms (Matrix, Air (Big-Mem version), Marmite etc.) designed for Jelly Bean but I never to seem get any greater ram than about 150-170 mb even on first boot with no applications installed and when I restore about 50 of my apps through titanium it goes down to 120-150 at max.
I have tried rebooting my device every now and then but the ram leak doesn't get any better.
That way most apps that I run crash my device (im a big fan of chrome on android but the lack of availability of free ram degrades performance)
I've been looking into using different free task managers on the play store but of no use.
Simply put, my question relates to the free ram this device can generate!
Can anyone give me an explanation as to the lack of free ram and what kernel, tips and tricks I could follow to improve it?
You can try flashing a kernel that supports BIGMEM(check the development section). Since you're new you won't be able to post any question regarding said mod. Basically gives you 50mb of extra RAM which, IIRC, takes away from the HD recording portion of the phone or something of that nature. The 512MB RAM sucks, but I never had an issue with it on mine. Then again, I never really ran a lot of applications. Android can handle the tasks on its own and free up memory when needed. But you may face a few launcher redraws now and then.
chronophase1 said:
You can try flashing a kernel that supports BIGMEM(check the development section). Since you're new you won't be able to post any question regarding said mod. Basically gives you 50mb of extra RAM which, IIRC, takes away from the HD recording portion of the phone or something of that nature. The 512MB RAM sucks, but I never had an issue with it on mine. Then again, I never really ran a lot of applications. Android can handle the tasks on its own and free up memory when needed. But you may face a few launcher redraws now and then.
Click to expand...
Click to collapse
Yeah so like you said I did try the Big Mem versions of Air Kernel and Matrix but it was never really of much use. Matrix gives me about 180 mb of ram when the device has no foreground apps running (except the system processes of course) and Air goes to about 140-160 not more.
The thing that I don't get is that this other friend runs Jelly Bean on his Galaxy S with Devil Kernel or something and his free ram is above 190-ish.
Technically both sport the same hardware with a few extras on Nexus S (led flash, lack of gorila glass, NFC etc.) but it really doesn't make sense.
And about those Launcher redraws. Yeah, they've been going really frequent now that I installed and use chrome as my daily browser.
Overall, in my experience I'd say Matrix Kernel would be perfect if it weren't for that Voodoo Colour Mod. It gives a weird hue to my display orangy in nature but Air comes around well in that department.
We all understand what you're experiencing. Basically, our Nexus S devices just are not able to keep up with the ever increasing size of electronic files. Even though it's nice to be able to run JB, it really stretches the Nexus to it's limits. I too am torn, because I love the smoothness of 4.1.1, but to be honest, the phone can handle GB much easier. One other thing, Chrome is a huge consumer of ram ... really too much for the NS. As much as I love my Nexus, the handwriting is on the wall, if I really want to continue to enjoy all the new stuff coming our way.
The colors can be adjusted to your liking. Some kernels have a setting that's not the factory norm(ie Trinity). You also have to keep in mind some of that RAM has to be dedicated to the OS itself. You're gonna have to deal with the fact the phone has a memory limitation on 4.1. Sucks, but there's really not much else you can really do about it.
I could never get above 125MB on GB even with a custom kernel. With only 512MB ram, more than half of that is already used by Android itself, there's not much left for apps. That said, I would remove unnecessary widgets on home screens, install Autostarts, or ROM Toolbox, or Gemini App Manager or other autostart management app and turn off autorun triggers on apps. The less background apps the more rams you can free up. I'm currently running with about 75MB and it's smooth. I set auto free rams to start killing apps if it's below 45MB.
Sent from my Nexus S using xda premium
[email protected] said:
I could never get above 125MB on GB even with a custom kernel. With only 512MB ram, more than half of that is already used by Android itself, there's not much left for apps. That said, I would remove unnecessary widgets on home screens, install Autostarts, or ROM Toolbox, or Gemini App Manager or other autostart management app and turn off autorun triggers on apps. The less background apps the more rams you can free up. I'm currently running with about 75MB and it's smooth. I set auto free rams to start killing apps if it's below 45MB.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Those auto triggers you talk of what software do you use to counter those cause I just looked at the cached processes inside the stock Application Manager and it showed a few that always show up when my phone boots. Of those that I usually encounter is Titanium, Maps, Google Search and a two or three more. Killing them doesn't make much of a difference though. Either the ram display at the bottom is screwed or the ram just doesn't go up when I abort any one of them and after a while they again show up. How do I deal with them?
Some general points.
Yes we want more ram. But we want it to use it. Free ram is wasted ram.
Task managers suck. All of them.
Low ram should not crash your device.
Stop worrying about how me free ram you have
Chrome sucks. It sucks on all devices. Sucks on n7. AOSP just runs better.
Want to keep a little more free ram because your device lags when its low on ram. Go to developer options and limit background processes
I'm with al. No point in over-obsessing about it. Cached processes aren't doing anything. They're there for when you want to switch apps for quicker access, which part of the way Android operates. You can limit what starts on startup to increase boot time(probably not even worth it), which I do even though I just said it probably doesn't help much, with a startup manager.
I to am no fan of task killers. I've heard that they can sometimes consume more ram since some of the killed apps will try to start again.
I found the autostarts app very useful. I have disabled around 50% of all auto starts. Mainly for installed apps but also a bunch of system apps. Another useful tool is Auto Memory Manager which sets the ram level where the system kills apps according to their category (e.g. Foregroud, visible, hidden etc). I use the "mild" manager with the level for empty apps raised. I manage to get around 80 MB free when running nothing. However I have a performance ROM which might affect that number.
My Nexus S has been retired a long time now.. I'm currently using the GS3 with lots of rams so it's not an issue for me anymore dealing with low rams... However, same symptoms on the GS3 or any Android phone, the less available rams means more processes are running which can cause slow app responsiveness. Also, some app even runs in the background hogging load of cpu usage, that definitely slows down your phone. I use task manager to kill off those high cpu apps when they go wild. OS Monitor is a good app for monitoring cpu usage... GO SMS Pro is an example app that sometimes persistently consumes 30% - 50% cpu, killling it off makes the phone smooth again.
S-beamed from my GSIII via xda premium
Hey guys... I have read so many statements and questions from members saying they only have 50.. or 100mb of RAM left. That their custom ROM takes up too much RAM or that their system is slow because of the lack of RAM...
So I created a video thats addresses this issue and hopefully will help new and old users alike....
The fact is that Android does an awesome job of managing applications and services that are running. Feel free to uninstall applications from your device that you don't use (like bloatware) but killing tasks all the time actually slows down your device. Android wants to fill its memory with applications that it think you will use. So clearing the RAM will only use more CPU power to full the RAM again
Thanks.
Spot on ! What can I say apart from this thread is bookmarked and the link will be posted next time we get another "Help ! wheres my RAM gone arrrrgggghhhh" thread. I can never see why people complain about RAM being used , You have it so use it !!!1!!!1
Most RAM killers give a placebo effect and to be honest they do slow your device down. Thanks for making the vid as it will be easier than typing out the same stuff again and again. A start up manager strategically used would be much more effective.
Off Topic : OH so thats what Orcs sound like ( The OP will get the joke , being a kiwi .....I hope lol )
Epic - that is all i can say ! Not a word un true
hamdogg said:
Hey guys... I have read so many statements and questions from members saying they only have 50.. or 100mb of RAM left. That their custom ROM takes up too much RAM or that their system is slow because of the lack of RAM...
So I created a video thats addresses this issue and hopefully will help new and old users alike....
The fact is that Android does an awesome job of managing applications and services that are running. Feel free to uninstall applications from your device that you don't use (like bloatware) but killing tasks all the time actually slows down your device. Android wants to fill its memory with applications that it think you will use. So clearing the RAM will only use more CPU power to full the RAM again
Click to expand...
Click to collapse
i see, but if it's like you said, what's the main point of making clearing RAM function available on android? Don't they make that for some purpose? If clearing the RAM / killing task slows down the android, then it shouldn't be there... should it?
According to Google IO's 2012 Android learns what applications you use more often and 'should' load them up. However if you believe its not doing that then the 'clear memory' function could be used. Also if you have a series of apps in there that you believe shouldn't be, thats also when you could use it.
I never touch the clear memory funciton..
I think that if google hadn't put that function in android, then its users would demand it so we have 'control' over our devices.
Which is whats missing from iOS right?
ASIDE: Yeah.. Perhaps I should change my location to Hobbion? or Isengard ... :b
cool stuff
Thanks