Related
Everyone knows computers, phones, pda, slows as the memory fills. Now there are ssome apps on the market that say they speed up you phone. So far I count three
- Memory up Professional
- Memory up Personal
- Memory for Lemmings
Has anyone tried any of these? What do you have to say about them? Do they work? Are you to skeptical (scarred) to try them?
I tried memory up Professional but didn't seem to work also its shareware
Memory for lemming seemed more simple but memory number keep jumping around there should be a log/graph for memory usage like windows task manager (I probably should email him that)
Haven't tried mem up personal though,
To an extend they work but overall they have no use. Android OS is built around killing services after some time and keeping the phone running in top performance. Those memory programs might free up a few KB's but not much use on that part, unless you have a program that allows you to kill services and stuff, which might have a practical use. Overall my answer is they are pretty much fake!
Just look at the definition of Lemming...
Lemming
The act of following the crowd into an investment that will inevitably head for disaster.
The version Memory for Lemmings is essentially garbage as well. He only made it to prove a point that the effects of the other pay programs are useless.
I used Memory Up when my G1 was working (doing a warranty, still waiting for the mail). It did not appear to do anything. Some claimed it did, I claim placebo effect for them.
The first thing I checked when running it was whether or not it killed open apps, it did not. Useless in my opinion. Wait for a real task manager.
From what I understand it does the same thing Oxios Memory does for Windows Mobile... it merely compacts RAM by clearing up system memory providing a slight boost but non noticeable to the human eye or feel. Android system by default will keep up to 6 applications running in the background and closes the oldest app. when the 7th application is opened (hold down the home key and try it out yourself). From what I have noticed, (and there is not real way to track virtual/RAM memory in the G1, if you don't turn off your phone but every few days... then the memory programs WILL help (slightly) to avoid the inevitable power off to clear system RAM or cool off the circuit board.
Lol welcome to the land of the stupid. I explain not only WHAT the app MemoryForLemmings does , but also HOW it does it right in the description. Not only that but I also suggest a google search term which tells you ALL ABOUT Garbage collection. But for the Google inept here we go.
Every java program has variables and objects in it. These objectd consume memory - both on the java heap and also indirectly the system. Now Old School coders like myself who used C generally null out the variables when done with them - thus freeing memory off the heap.(I am not going to explain what the heap is ****ing look it up), we are used to C where every spec of memory had to be allocated and deallocated. Java on the other hand doesnt require you to be so fussy, It keeps a running log of variables etc and whether they are being used or not and periodically it will go through and run .... wait for it ... garbage collection. It does this at a set time or at a set memory level of the heap.
But guess what, Sun in their infinite wisdom provide a way to ask the system to run garbage collection early. This is not a forced suggestion merely a hint to the OS, the OS can choose to ignore this. Guess what my app does? Can you guess? Thats right it merely suggests to the OS to finalize items thats may be running but are old and to run garbage collection. Thats it. The whole damn program is maybe 40 lines long and that includes the Dialog code.
There is nothing like a bunch of non coders getting together on a forum to write up some of the least correct assumptions I have ever seen about code.
Android does not close apps on a First in First out basis. You cannot rely on that when coding apps, Androids program management is more sophisticated than that. You cannot "compact RAM" it is not disk. Any clearing of the system memory is a crap shoot, I Included it on the app for ****s and giggles. It may speed up your system as the heap/system memory clear, but again that's a crap shoot.
I only wrote the app at all so the idiot charging 15 bucks for app wouldn't be able to scam people for something the OS would do anyway (Which by the way is ALSO in the description). I didn't even post it to the market to start just the androidcommunity boards, but they encouraged me to list it.
I really suggest you actually USE google (Golly where would you find a google search bar), before you go off half cocked.
Bratag said:
I really suggest you actually USE google (Golly where would you find a google search bar), before you go off half cocked.
Click to expand...
Click to collapse
I don't think half the visitors to xda-dev Dream understood what you wrote above. And that's why people will continue to buy these apps (on this and other platforms). Right now the Android Market is still not as bad as the iPhone App Store, where exploitation and ridiculously pointless apps hit truly saddening new plateaus.
I think i'll go write a "cell phone radiation reducer" app right now and charge twenty bucks for it.
jashsu said:
I don't think half the visitors to xda-dev Dream understood what you wrote above. And that's why people will continue to buy these apps (on this and other platforms). Right now the Android Market is still not as bad as the iPhone App Store, where exploitation and ridiculously pointless apps hit truly saddening new plateaus.
I think i'll go write a "cell phone radiation reducer" app right now and charge twenty bucks for it.
Click to expand...
Click to collapse
Sweet Ill totally buy it
I sometimes feel I am one man trying hold back the tide of stupid armed only with a soggy celery stalk.
Java?
Bratag said:
But guess what, Sun in their infinite wisdom provide a way to ask the system to run garbage collection early. This is not a forced suggestion merely a hint to the OS, the OS can choose to ignore this. Guess what my app does? Can you guess? Thats right it merely suggests to the OS to finalize items thats may be running but are old and to run garbage collection. Thats it. The whole damn program is maybe 40 lines long and that includes the Dialog code.
Click to expand...
Click to collapse
Bratag: All of the apps on my system run in Linux, not Java. So your program wouldn't really do anything for me or the 90% of android users that don't do Java? I'm not sure about the Linux/Java connection you are making. Please elaborate.
The dalvik vm is basically a tweaked java vm. With some very limited exception, almost all the code in the available apks are all java classes.
Bratag said:
There is nothing like a bunch of non coders getting together on a forum to write up some of the least correct assumptions I have ever seen about code.
Click to expand...
Click to collapse
You must be new here.
texasaggie1 said:
Bratag: All of the apps on my system run in Linux, not Java. So your program wouldn't really do anything for me or the 90% of android users that don't do Java? I'm not sure about the Linux/Java connection you are making. Please elaborate.
Click to expand...
Click to collapse
Actually all the apps on your system run In a Java Runtime Environment called Dalvik which is a virtual machine which has been optimized to efficiently run multiple instances efficiently. So everything you run is a java app and that includes the desktop.
Now this all runs on TOP of a linux KERNEL.
EDIT: damn someone beat me to it
Bratag - you rock.
Bratag said:
Actually all the apps on your system run In a Java Runtime Environment called Dalvik which is a virtual machine which has been optimized to efficiently run multiple instances efficiently. So everything you run is a java app and that includes the desktop.
Now this all runs on TOP of a linux KERNEL.
EDIT: damn someone beat me to it
Click to expand...
Click to collapse
The very reason an emulater like Smartgear, Pocketnes or MAME is impossible on Android. A black & white Gamboy emu would kill the 7201a with sound and 30fps.
Java sucks for these type of apps having to emulate the game system and be interpreted through two layers.
rushless said:
The very reason an emulater like Smartgear, Pocketnes or MAME is impossible on Android.
Click to expand...
Click to collapse
Not at all impossible if you use JNI to hook to a compiled c++ or asm library for the main engine. Heck, it's not even "impossible" to do in Java-- merely unfeasible.
Stay on topic.
Apps on Android can't touch anything outside their own sandbox due to the security model (unless the other app gives you a way to access it's data, but even then, you can't touch it's memory). I feel sorry for the poor sod who pays for these apps.
Not sure if you all are familiar with this app, I haven't seen anyone speak upon it on XDA yet, so just thought I'd share my experience with it.
http://www.androlib.com/android.application.com-lim-android-automemman-wBjq.aspx
IMO, this app is pretty cool. Very simple and easy to use, although it doesn't come with detailed instructions on how to use, so I felt the need to explain a little bit about it:
Tired of lags to and from Dialer/Contacts/Call Log?
Have you ever pressed the call button to dial a number/contact and nothing happens for 10 to 15 seconds then finally the call goes through and starts to ring?
Ever went back to home screen after fooling around with an app, or web surfing the browser only to find that a widget or two is missing or is not loading/refreshing properly?
Gmail not syncing daily as it usually does?
Market taking forever to load up the downloads page or lagging connection with G-talk to promptly start the download/updates you started?
Well these are the memory/background/content provider situations that need to stay snappy if nothing else does, agree?
Then this app may or may not be the answer to all of your problems.
For me it was. First and foremost, it is a FREE app, yay! (at least to my current knowledge, unless developer has changed it)
*FYI* This app does require root permissions, so if you are not rooted this will be of no use to you.
After installing, when first opening the app, super permissions should pop up, just check the always box and press allow for root access. Close the app, then re-open.
Now, there are 4 options you may choose, DEFAULT< CUSTOM< MILD< AGGRESSIVE
Default settings will be what you see on first use, those are the default Android memory settings for your G1
Custom- self explanatory, you move the bars of each memory category according to how you prefer- *Note* the amount shown is not exact memory, it is a threshold, basically a set amount not to exceed, Your phone will automatically choose how much to use according to how much it needs, but its limitations will be set by the threshold you choose. Go ahead and make your adjustments, then click the custom button, this will save these settings. So the next time you want to re-enter those settings, just hit the custom button, and it will restore.
Mild- Simply a preset application setting
Aggressive- Another preset app setting
You choose what works best for you, I would suggest playing around with different settings until you have achieved a memory usage that gives you the most improvement, *Note* Do note mistake this as a speed app, it only controls memory, so don't expect some super fast change, but if you set it up properly, and memory is being managed to the best case scenario of your usage, speed will increase, believe me.
Start with the presets, see how they work throughout the day, if you notice no difference, or worst than it already was, change it to something else.
Personally, my best experience has been with the Aggressive preset. Its been the most effective for my phone, however; this won't be the case for everyone. Aggressive basically raises the threshold for background data(widgets,home, cache, etc.) And content provider (google apps, settings, G-talk and stuff) And Empty application- this means, IMO, the amount of free memory sitting around available, for soon to come data or apps that you might open later, I.E.- multi-tasking, Call screen, new mms or sms
It also lowers the threshold of the foreground and running apps, so that they don't suck up so much memory the phone lags before it can open other things in memory. Get it? But as I stated, different people will have different preferences.
If you haven't already, try it out! If you don't like it, or don't need it...maybe results won't change things enough for you to have any use for it, you can always uninstall, and it won't harm any memory or data on your phone.
Also, regardless of threshold settings, if you open or use more memory than threshold limits, it will not break or crash you phone causing reboots or anything like that. So don't worry. The app does not prevent you from doing anything on your phone, it simply manages it according to your use.
I hope this comes in handy for someone, as it has been more than useful for me on a daily basis. You can find more information via market or the link above.
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
I could be wrong, but I believe the intent of this is to allow the Android internal memory manager to be tweaked so that certain applications/processes have a higher priority and remain in memory and those that you deem as "less important" are removed first.
Here is a thread on the Hero forum about it:
http://forum.xda-developers.com/showthread.php?t=622666
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
With this App, I do not notice an increase in free (meaning useless) memory... I do notice that key processes that I deem important are still running on CM 4.2.14.1... Even after running many of the ~160 apps I have, including games...
Individual results may vary... Nobody runs the same exact configuration and apps on their G1...
L8r
@Ibcoder
That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Also, here is another App that does the same thing... only it will allow the settings to persist through a reboot...
http://www.androlib.com/android.application.com-rs-autokiller-wEwp.aspx
Click to expand...
Click to collapse
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
TeeJay3800 said:
I recently saw this new app in the Market, but was unsure what advantage it will have on performance, if any. I'll pay attention to this thread to see where the discussion leads on it's usefulness (or potential lack thereof).
Click to expand...
Click to collapse
Ok, and I don't blame ya, that's how I test everything on xda, roms,apps, hacks, you name it....but only after I review enough good responses (preferably 3)
But on the contrary, there have been times that something was reviewed poorly, but after my own experience turned out to be great! You'll see that a lot in the android market as well, great apps with two star/3 star ratings all because some asshole didn't know how to use it, LoL
Try it dude, you got nothing to lose...won't break ya phone, but if ya want to play safe nandroid your current stuff first.
Klyentel said:
Cool app! Thanks for the link, never seen this one.
But wouldn't auto kill be the same as all the other task managers and explorer apps? Its made to kill off unwanted apps, processes, and background services to free memory right? Well, I have plenty of those, and they all work quite fine.
The app I am discussing above is not a killer, its only a manager, it just gives the proper amount of memory to the category you specify to be more important memory users, thus for saving wasted memory. It doesn't specifically kill off or make memory, just manages it.
thanx though, I will try that out.
Click to expand...
Click to collapse
As far as I know, they are pretty much the same... The XDA thread I mentioned above has both the Dev of the App you posted and the Dev of the App I posted... They both created one at around the same time... One with sliders and one with fields... The only difference I think is that AutoKiller uses a service to write the settings on a reboot...
Still playing with this to see if it makes any real difference... I know if I set the values too aggressive, then the browser reloads every time I come back to it...
I know if I set the values too aggressive, then the browser reloads every time I come back to it
Click to expand...
Click to collapse
yeah that has happened to me too.
The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
lbcoder said:
Don't take offence to this, but any "speedup" you think you are getting from it is entirely a function of the placebo effect.
There is no advantage to forcing memory to remain "free", and in fact, doing something like this will actually make the phone SLOWER than it would otherwise be.
Android has a VERY well thought out memory management system. It keeps a record of processes running and their priorities. In the event that more memory is required for a higher priority application, it will automatically select some other application to kill off in order to get that.
What this does is it ensures that you ALWAYS have the memory FULLY utilized, which means optimal performance under every circumstance.
An unfortunate trap that you are falling into is the traditional view of memory -- for example on a DESKTOP system, you don't have anything killing off unused processes, which means that every program you open will use up more memory, so the more FREE memory you have, the more new programs you can open before it starts swapping, and therefore you aim to always have a big chunk of free memory because more free memory means more applications can be open.
Android doesn't work like this!!!
What you are doing is forcing a memory utilization threshold on the thing. This has the same effect as simply reducing the total memory available on the device. That means that important applications are *MORE LIKELY TO GET KILLED OFF*.... which has exactly the OPPOSITE effect from what you seem to be after, which is to ensure that these important applications are NOT killed off.
Click to expand...
Click to collapse
@dwang-agreed, as I stated @lbcoder, what he is saying is that the app holds everything in memory which slows down system, but it does not do that, and he implied that I stated it limited use of apps, which is incorrect, it does not operate as a limiter, or a kill switch, only a manager. Sort of like, organizing processes by priority based upon setting of threshold tolerance. Of course killing off unwanted apps and processes have to be done manually, via kill widgets or file explorers, When I first posted about this app I assumed that concept to be in mind of the reader....sadly I was wrong. I guess everything around here has to be put in perspective as if the reader knows nothing...sort of like an "101 handbook for Dummies" type thing.
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Klyentel said:
@Ibcoder
But it doesn't do that, the threshold simply states a measurable amount of reserve...but not a limitation. Theres a difference. Limits and thresholds are not the same, So what you are saying is not how the app works. All apps open in memory remain in memory, of course you still have to use kill switches and task managers to control unwanted memory hogs, but the app basically controls the memory in use, thats all Im saying, so if that memory is being divided properly, responsive times will increase, I know android had its own setting of doing this, hence the word *DEFAULT*...that is what the app is for, if you don't want to let Android control your memory usage, the app gives you the option to customize it
Click to expand...
Click to collapse
lbcoder said:
What you are suggesting is incorrect, contrary to the product description, and quite frankly, impossible.
And you can't read.
There is no "I" in lbcoder.
Click to expand...
Click to collapse
First and foremost buddy, I quite frankly don't give a dam how you spell your name with an "I" or an "L"
Secondly, what I am stating is not incorrect, and is possible, because I have the app, use it everyday, and does exactly what I said it does via OP. Thank you very much. If you disagree, then don't download the app. Simple as that.
or heres a better idea create one of your own. I will be more than happy to try it if you feel you can do better, but don't downsize the quality of this one, straying other users away from trying it, as it may be as useful to them as it is me. Got it?
Now get ya DREAM on...(with android that is )
and leave me alone.
After fixing some lags with I/O system by using filesystem LagFix I still have a Lag problem in my system and I think it's not related to Samsung.
I think this could be an Android problem.
After a fresh reboot I get 124MB of free RAM.
BUT... every day I need to reboot the phone because after 3 hours it became laggy.
Now I analysed this and read a bit about the memory management on several forums and was able to reproduce the lag 2minutes after reboot.
I just need to use much applications one after another to raise the RAM usage for every application.
When the free RAM reaches 40MB I think the system clears some pieces for using it for the app I now want to use and there is the LAG.
Is there any fix for Android not caching every activity of an application in the RAM?
Now for me Android feels like: Usage -> Full RAM -> Lag
Sorry for the new thread but after 2 hours of research I didn't find anything useful over search function.
Yea, every program should have as much ram available as their size. 2gig for program storage on sgs, so there should be the same amount of ram ;D Anyway, theres still less memory for programs on the sgs than for example in the N1. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Sent from my GT-I9000 using XDA App
Not just the RAM for the apps... there's much more...all mails from internet, all google talk conversations, the wather I checked out from internet with any widget, feels like every interaction is cached into the RAM until it reaches the 40mb mark and after that every interaction on my system is laggy... for example: opening the notification bar needs 2-3 seconds.
I already talked to N1 users with the same problem
DasLeo said:
I already talked to N1 users with the same problem
Click to expand...
Click to collapse
Heading out the door in a minute so can't comment on the rest, but I strongly disagree with that part of your statement.
As an N1 owner I've NEVER seen lag like I suffer on the SGS. Never seen the absolute FREEZE in the GUI like the SGS gets.
I'm running FroYo on the N1 now, so can't compare side-by-side to the SGS things like memory usage, but I don't think that's the issue here if you're going to use the N1 as a comparison, despite other users complaining of lag.
You might try Autokiller or the free memory manager app from the Market and see if that improves thing, they'll keep more or less memory free depending on settings. You could test how soon lag comes with default, minimal, and aggressive settings.
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
rkantos said:
. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Click to expand...
Click to collapse
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Guys please,
Getting off-topic here. Here is Android Development.
Not Q&A or General.
Please post in the right section.
Here is getting too many off-topics that pose no relation to Android Development.
Too cluttered.
Thanks
DasLeo said:
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Click to expand...
Click to collapse
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
I use Memory Booster Lite (free version) app to free up memory, must do that manually but it works very well, if you buy the app it free up memory automaticly.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
The phone does have 512mb of ram. It just isn't used properly.
MOJO783010 said:
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, wrong. The reserved ram is in the form of a ram disk, which seems to be a bit oversized. Not really sure why a ram disk is needed at all, personally.
sammy555 said:
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
Click to expand...
Click to collapse
This is the correct solution. the JF* series of firmwares have very bad default settings for killing unused apps. Use this app to set them a bit better and you shouldn't have any problems.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
It does have 512 of ram, but some is partitioned off for the phone, so that you can always receive phone calls. Just about every device does this, because users would be more upset if they couldn't pick up the phone until they had closed a bundle of running programs. Don't you think that people here would have noticed earlier if the SGS physically had less ram than claimed ?
As far as the OP is concerned, sounds like you are just running too many programs at once. Its not an android problem, its user error.
Any task manager, but particularly an auto-killer will set you right, although alternatively you could try not leaving every app open when you're finished with it. You think your PC would run ok if you left one game open while you opened another ?
DasLeo said:
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Click to expand...
Click to collapse
I wasn't comparing a N1 on FroYo to the SGS on Eclair. My comments were in regard to when I was on Eclair, which was several months...FroYo's only been available for a couple of months. What I said was since I'm on FroYo now, I can't compare side-by-side, but my experience with an N1 on Eclair was never any lag problem or GUI freezes.
Anyways, I also suggested you try Autokiller, and you missed that or misunderstood it by saying you already run a Task Killer (which is generally considered a bad idea, but I see you picked up on Autokiller after someone else suggested it. Enjoy.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
Nah, all phones advertise the actual chip size in it, not the amount the system actually lets you use.
tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
Thank you. This removes almost all lag I'm experiencing.
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
douginoz said:
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
Click to expand...
Click to collapse
Try enabling zram, I haven't tried it personally but its supposed to allow for more multitasking.
Sent from my Nexus One using xda app-developers app
Moved To Q&A
You may of considered it dev based, but its a question so belongs in the Q&A section.
I've tried ZRAM now for a couple of days but makes no difference. I also have the problem on another Android device. I'm convinced its some sort of design limitation of the opsys or something. When I start up Grindr, it takes a long time to load all the images, make connections, etc. Then I start of Gruff, and it does the same. As long as I don't try to go to another app, I can flip between the two of them without them restarting/reloading/reinitialising themselves. That is clearly because their pages didn't get swapped out of memory or flagged for deletion and deleted.
But if I do something else, or even try to use additional functions within either app, its too much and the next time I try to flip to the other app, it has to reload and reestablish connections etc.
Its not just those apps either. The same with a game like Candy Crush. Or many many apps.
So either my devices don't have enough memory of some form to allow many concurrent apps to run without being swapped out, or Android can't handle it and unnecessarily swaps out or deletes a process's memory pages to make room for the next process, >>> even if the device has plenty of memory<<<.
I don't know which type of memory the opsys needs if this is the case. I'd like to know so that i can make sure there's ample available so that this constant restarting doesn't keep happening. It seems stupid to me that Android does this if the device has got "heaps" of available memory (no pun intended). Newer devices will continually have more and more built in memory, so if Android is doing this arbitrarily and not because of space issues then its, well, stupid.
I have to assume its my devices that are the problem. They're both old (Nook Color, Nexus One). But with the NC, I'd assume we can partition some of that 5GB for use as main memory to run lots of processes concurrently, without this annoying swapping/page deletion/forcing re-inits all the time.
I'm also having problems figuring out where in XDA to post this question - its not NC specific, or dev specific, but I need answers from people that know the Android architecture so I can work out if its possible to stop this from happening.
Hello everyone.
Even after hibernating all the apps, still 2GB of my ram is used. I want to look at all the processes that are using the ram. How can I do that?
Cheers!
Until someone comes up with a better answer...
Settings/Apps. Under each app there are stats for used storage and memory used in the past few hours. Might give you a clue.
xhamadeex said:
Hello everyone.
Even after hibernating all the apps, still 2GB of my ram is used. I want to look at all the processes that are using the ram. How can I do that?
Cheers!
Click to expand...
Click to collapse
Because ANDROID KNOWS that UNUSED RAM is WASTED RAM.
It ***preloads*** all of the things, in order of what it believes is the likelihood of you using those particular things.
This way when you actually DO use one of those things, it is ***already loaded*** (and starts fast).
Stop "hibernating" things. You are breaking Android.
doitright said:
Because ANDROID KNOWS that UNUSED RAM is WASTED RAM.
It ***preloads*** all of the things, in order of what it believes is the likelihood of you using those particular things.
This way when you actually DO use one of those things, it is ***already loaded*** (and starts fast).
Stop "hibernating" things. You are breaking Android.
Click to expand...
Click to collapse
Hmm.. You have a point..
So, is using Greenify a bad Idea?
xhamadeex said:
Hmm.. You have a point..
So, is using Greenify a bad Idea?
Click to expand...
Click to collapse
Bad idea.
yea there's two built-in ways to view running processes. One is directly Settings. Scroll down to where it says Memory. Open and check it out. I know. Google might as well not even wasted their time making that activity since it's next to useless. The other one is located in Developer Options. It's labeled "Running Services" and gives you stats on what apps are running, how long, etc. Yea, not very helpful either since there isn't much you can do besides uninstall some things or do the root and ransack thing. It's intentionally made like that, just like the way android battery stats are completely useless for nailing down offensive background services. Google likes it that way. They make money by tracking your location and serving you up with as many ads as possible. While it's true what dude said about the way Android preloads and makes a lot of stuff ready in RAM, hibernating, and using task killers is basically like working against your system resources, don't listen to people who yell things at you because they've been brainwashed by companies and developers who want their services installed, front-and-center, autostarting, and running 24/7 in your device's memory. Why else you think every website has a banner talkin' bout "oooh ooh install our app" and grant as many permissions as possible while some even go as far as sabotaging their own services via their website so users feel forced to install the app. They don't care about you, your cpu, or your experience as long as it's filled with ads and periodically uploading analytics and usage stats and the best way to do that is to have background and persistent services to silently restart their location polling or pointless notification systems designed solely around getting you to interact with the app. I'm not talking about things like email, messaging, or whatever other app you depend on or feel is important enough to keep close at a tap of finger. My suggestion is to analyze those settings activities I named earlier or a 3rd party one like BBS and make some decisions about what you are willing to delete. Compromises can be made depending on what's important to you and also with root. Half (or more) of the apps in your phone that have boot receivers and other various event listeners up the wazoo have no business knowing your phone is even on until you tap it's little icon. This is opinion of course because others will tell you you're breaking android and a bunch of other nonsense they've been fed by google to address the people, like me, who are tired of seeing google and other apps (usually ones my by behemoth corporations) that run constantly in the background even though I open up and use whatever particular app maybe once a week. If you're rooted, there is a lot you can do to take control of apps that like to stay nudged up as close as possible in the queue and keep open connections. It all depends on you and how you use your device. Don't listen to know-it-alls who yell at you IN ALL CAPS. Either accept the fact that google, facebook, admob (and whoever else app you have that thinks it's the most important) own your phone, or do a little research for yourself because regardless of what homeboy said, it's easy to see that available RAM feels way smoother than ram that has to wait for android to move pokey balls out of the way...just sayin
ElwOOd_CbGp said:
yea there's two built-in ways to view running processes. One is directly Settings. Scroll down to where it says Memory. Open and check it out. I know. Google might as well not even wasted their time making that activity since it's next to useless. The other one is located in Developer Options. It's labeled "Running Services" and gives you stats on what apps are running, how long, etc. Yea, not very helpful either since there isn't much you can do besides uninstall some things or do the root and ransack thing. It's intentionally made like that, just like the way android battery stats are completely useless for nailing down offensive background services. Google likes it that way. They make money by tracking your location and serving you up with as many ads as possible. While it's true what dude said about the way Android preloads and makes a lot of stuff ready in RAM, hibernating, and using task killers is basically like working against your system resources, don't listen to people who yell things at you because they've been brainwashed by companies and developers who want their services installed, autostarting, and running 24/7 in your device. Why else you think every website has a banner talkin' bout "oooh ooh install our app" and grant as many permissions as possible while some even go as far as sabotaging their own services via their website so users feel forced to install the app. They don't care about you, your cpu, or your experience as long as it's filled with ads and periodically uploading analytics and usage stats and the best way to do that is to have background and persistent services to silently restart their location polling or pointless notification systems designed solely around getting you to interact with the app. I'm not talking about things like email, messaging, or whatever other app you depend on or feel is important enough to keep close at a tap of finger. My suggestion is to analyze those settings activities I named earlier or a 3rd party one like BBS and make some decisions about what you are willing to delete. Compromises can be made depending on what's important to you and also with root. Half (or more) of the apps in your phone that have boot receivers and other various event listeners up the wazoo have no business knowing your phone is even on until you tap it's little icon. This is opinion of course because others will tell you you're breaking android and a bunch of other nonsense they've been fed by google to address the people, like me, who are tired of seeing google and other apps (usually ones my by behemoth corporations) that run constantly in the background even though I open up and use whatever particular app maybe once a week. If you're rooted, there is a lot you can do to take control of apps that like to stay nudged up as close as possible in the queue and keep open connections. It all depends on you and how you use your device. Don't listen to know-it-alls who yell at you IN ALL CAPS. Either accept the fact that google, facebook, admob (and whoever else app you have that thinks it's the most important) own your phone, or do a little research for yourself because regardless of what homeboy said, it's easy to see that available RAM feels way smoother than ram that has to wait for android to move pokey balls out of the way...just sayin
Click to expand...
Click to collapse
Holy wall of text Batman!
You've got a couple of points hidden inside that rambling, but dude... If you want anyone to read that, try that little thing called paragraphs.
Didgeridoohan said:
Holy wall of text Batman!
You've got a couple of points hidden inside that rambling, but dude... If you want anyone to read that, try that little thing called paragraphs.
Click to expand...
Click to collapse
Ah...apologies. I may have been a little bit hopped up last night on the leftover holiday spirits but how else to explain what I see as google's all-over-the-place ridiculous approach at making it as god awful experience as possible for people interested in granular control over their devices' /system. I just got done flashing, setting up, and going thru the motions on a new phone so I may have been a little annoyed as well. lolz hope it helps someone.