Related
Can anyone explain the amount of RAM that this phone is suppose to have?
The specs for the phone lists 768 MB. However, the total memory that comes up is 617940 kB.
Thanks.
Bull Shot said:
Can anyone explain the amount of RAM that this phone is suppose to have?
The specs for the phone lists 768 MB. However, the total memory that comes up is 617940 kB.
Thanks.
Click to expand...
Click to collapse
where are you finding this number? i am at 758 MB. since i have a bunch of apps installed, that would seem about right.
How are you guys getting so much free ram? When I check on Task Killer, whenever I kill all the apps I'm not using it usually shows 358 mb ... and programs I'm not using automatically keep running (i.e Maps).
hmm maybe im not checking the right place? i'm getting my 758 mb number from settings--SD and phone storage. the internal phone storage tells me 758mb.
on an unrelated note though, you shouldn't use task killers. they are considered by most to be more of a drain on your battery life as android is already setup to manage closing unused apps on its own.
Many people use the term "memory" to mean system memory as well as storage. I try to avoid calling system storage as "memory" and tend to use "storage" instead, or refer to the type of storage.
Total ram is around 768mb. Part of it is reserved (not sure why, possibly for filesystem caching) so around 603mb is available. For this platform that is a healthy chunk of RAM to work with. Even with my hefty usage I have ~126mb free.
Internal storage is something like 2gb, with it partially consumed by the Android install as well as NAND configuration adjustments for reliability which cause some of the storage space to be consumed through hardware (there's an excellent explanation of this somewhere, don't have a link handy), resulting in about 1.1gb being available. I have 103 apps installed, 523.5mb of the internal storage used, with 638.8mb available.
There was an excellent tool posted on xda (http://forum.xda-developers.com/showthread.php?t=1066060) called Android Optimizer that gives a lot of good information about memory, storage, cpu usage, etc. I'd recommend checking it out. It's not available on the market and it is a little buggy so use it with a bit of caution if you choose to use any of the optimization functions.
cool. thanks for the explanation nimdae!
There have been so, so, so many posts on this topic that I will not rehash them all here. Instead, I will ask a simple question: For what do you use all that free RAM?
Ask yourself that question, and be serious about it. I think you will find yourself uninstalling your task managers and memory optimizers before long.
Edit: to avoid unnecessary discussion, Watchdog is in fact neither of those, and I would highly recommend it as the only memory app you will ever need.
Edit 2: the total RAM displayed is the RAM that is actually available to be used by anything the user may want to run. As a poster earlier said, the system reserves a certain amount of RAM for its own use to keep important processes moving along. The reserved RAM is not available, and so doesn't appear in total RAM. Unless you want to uninstall the OS. Then you could have access to all 768 MBs.
I would like to reiterate why you should not use automatic task killers.
As of, I believe, Android 2.0, the garbage collection and memory management was significantly improved. However, this was not a new system in Android, it always existed.
How it works:
If you haven't noticed with Android, when you leave an app, it doesn't close it unless the app specifically does something to end the process. This is by design. Android allows the app to remain in memory. Frequently used apps will load faster with this design. A "task" that is not killed and is in the background ONLY consumes memory, it does not "run" (in Linux terms, the process is actually in a "stopped" state so the task can't do anything anyway). Only a "service" can run in the background. Most apps that have long running services have lightweight services.
If an application loads that requires more memory than is available, Android will examine backgrounded tasks for candidates to be killed to free up memory. This makes it so as many tasks as possible can remain in memory for better performance. In understanding this, you should know that if you have a large amount of memory, and memory usage is high, this is a GOOD THING. With the amount of memory in the I2, there is a lot of breathing space for this.
There is one other case where a backgrounded task will be killed: if it has been in the background for a certain period of time without being brought forward. Killing a task to free up memory to load another task can actually be a little cpu expensive (but not THAT much) so this can make it slightly easier.
Please note that backgrounded tasks WILL NOT contribute to battery drain. Only tasks at the front and services will. Killing your backgrounded calculator will do nothing for you other than free that small amount of memory it uses. Used memory does not contribute to extra battery drain as DRAM refreshes happen on ALL cells anyway.
Background services can also be made candidates for being killed. If an app needs more memory than can be made available by killing backgrounded tasks, then services become targets to be killed as well.
Automatic task killers cause a couple of problems. A less major problem is you lose that one benefit you get by keeping tasks in the background: performance. I don't just mean how fast it loads. If it can bring a backgrounded task to the front from memory rather than load from storage, you remove extra processing to load the app, including storage access, that contribute to higher battery drain. The other problem is a poorly configured task killer can break things like notifications.
Managing your services is always a good idea. Having a lot of services running means background processes that are capable of contributing to battery drain. Additionally, there are apps with misbehaving services (services that consume resources or use features they shouldn't). While I'm against automatic task killers, using something to monitor and manage services is a good idea. Just always keep in mind the implications for killing a service: it may affect a feature to an app that you would rather not impact.
Excellent explanation nimdae! Task killers are the devil.
On another note, my posts are getting too long...
nimdae said:
On another note, my posts are getting too long...
Click to expand...
Click to collapse
Everything is longer in Texas.
xgunther said:
Everything is longer in Texas.
Click to expand...
Click to collapse
That's what s...no, that's too easy.
Move along, nothing to see.
Before I read this I was like a task Nazi. I killed my tasks often, but now I think I will just let them be. Nice write up BTW. Very informative.
Sent from my ADR6350 using XDA App
TB13 said:
Before I read this I was like a task Nazi. I killed my tasks often, but now I think I will just let them be. Nice write up BTW. Very informative.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Remember: I'm not saying don't manage things. Poorly behaving services are the #1 cause of high battery drain (at least on non-LTE devices), and this will be even more problematic when you overclock.
xgunther said:
Excellent explanation nimdae! Task killers are the devil.
Click to expand...
Click to collapse
I tried not using them and I get better battery life with them...I use it maybe 3 times a day after heavy multi tasking. It's to each their own..but I see results for it..like 5 extra hours.
Sent from my ADR6350 using XDA Premium App
knipp21 said:
I tried not using them and I get better battery life with them...I use it maybe 3 times a day after heavy multi tasking. It's to each their own..but I see results for it..like 5 extra hours.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
If you get that much extra, you have a misbehaving app. Better to get the app developer to fix it or find an alternative.
nimdae said:
If you get that much extra, you have a misbehaving app. Better to get the app developer to fix it or find an alternative.
Click to expand...
Click to collapse
True, I don't need to use it often though lol
Sent from my ADR6350 using XDA Premium App
I'm in Texas as well.
sent from a phone without root.
I use a task killer only to manually kill an app that freezes or something. Its easier than going to manage applications. I have the autokill disabled.
Sent from my ADR6350 using XDA Premium App
AngelsPunishment said:
I use a task killer only to manually kill an app that freezes or something. Its easier than going to manage applications. I have the autokill disabled.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
CyanogenMod (maybe other ROMs) have a feature to kill a frozen app by holding the back button (long press, whatever). However, this can also be an annoyance on systems where for unknown reasons it registers a long press on a tap (my eris did this a lot).
I installed a single widget from Beautiful Widget yesterday and today I've had the launcher redraw itself multiple times and this is aomethig I've never seen before. How much free RAM should be available? I'm hovering around 120. Stock Nex HSPA running 4.0.1 on T-Mobile.
Sent from my Xoom using Tapatalk
I usually hover around 350mb free... 120 is seeming a little low. Are you exiting apps with the home button or the back button?
Sent from my GSM Galaxy Nexus
Either or, no preference either way.
Sent from my Xoom using Tapatalk
Are you stock?
Sent from my Xoom using Tapatalk
Often i stay around 120mb free ram so i think you are functioning normally.
Free ram is unused ram.
You only need as much free ram as the next, uncached task will require. On Android this is unlikely to ever be more than 80MB.
On this basis, if you have 120 free you should be fine.
djmcnz said:
Free ram is unused ram.
You only need as much free ram as the next, uncached task will require. On Android this is unlikely to ever be more than 80MB.
On this basis, if you have 120 free you should be fine.
Click to expand...
Click to collapse
Uh no. Free RAM consists of cached but not currently running apps and cached kernel resources. It is by no means "unused".
You also need a lot more free RAM than what the next app you are going to run requires, due to kernel caches and paging policy problems. If you are actually interested in learning how memory management works I suggest you read up on virtual memory first before giving others advice.
Chirality said:
Uh no. Free RAM consists of cached but not currently running apps. It is by no means "unused".
You also need a lot more free RAM than what the next app you are going to run requires, due to kernel caches and paging policy problems. If you are actually interested in learning how memory management works I suggest you read up on virtual memory first before giving others advice.
Click to expand...
Click to collapse
Don't be snide, it's unbecoming.
"Free" in the context that the OP used it is exactly that, free and unused - as in not used by anything at all, empty. Perhaps you might want to look that one up.
I responded to him in context and accurately. From an end user perspective it's a more helpful answer than a technical one about paging, caches and kernels...
I suggest downloading Cache Cleaner NG (yes, the "NG" one) from the Market if you're having lag or other problems. This will help no matter which definition of "free RAM" you choose to adopt I can say, though, that in my experience a lot of lag and force close issues have had more to do with cache and app data than with "free RAM." For example, on my Fascinate I'd have 120 MB or so of "free RAM" according to my system settings, but I'd still have major lag and more force closes than a chain of Circuit City stores until I cleared app cache using Cache Cleaner NG. This is different from wiping the cache partition in recovery.
Terminators run on Android
djmcnz said:
Don't be snide, it's unbecoming.
"Free" in the context that the OP used it is exactly that, free and unused - as in not used by anything at all, empty. Perhaps you might want to look that one up.
I responded to him in context and accurately. From an end user perspective it's a more helpful answer than a technical one about paging, caches and kernels...
Click to expand...
Click to collapse
Free in the context? There is no context needed here, as there is no ambiguity. Free here refers to exactly one thing: the amount of free memory reported by the Android system. The Android system uses a Linux kernel and reports free memory the way all Linux systems report free memory: all kernel and userland caches are reported as free memory. Free memory is not unused memory. Free memory is physical memory pages that are not currently marked in use by any virtual page entries. Free memory is used as cache by the virtual memory system. If you understand the virtual memory system at all you'd realize that truly "free and unused" memory doesn't even make sense in a virtual memory system. Truly unused memory is just cold cache, once the cache has been warmed up, the idea of unused memory becomes irrelevant.
Basically OP, you should never have to worry about it. This phone has more than enough RAM to handle anything you throw at it. If it ever feels "sluggish" just give it a reboot. No need chasing your tail to free up 15MB of RAM that won't make a difference anyways.
Thank you. This is what I figured as I've had quite a bit of experience with Android dating back to the G1 (it's why I don't have a task killer installed). Yeah, the lag is annoying although it's way better than my Xoom's. I was just wondering what you guys were hovering at.
I do have an app that turns itself on in my running apps list (it's ESPN's Fantasy Football app) I want to keep the app but it's sort of annoying seeing it pop up there all the time. Is there a way I can force it to stay off?
BlazinGTI said:
Thank you. This is what I figured as I've had quite a bit of experience with Android dating back to the G1 (it's why I don't have a task killer installed). Yeah, the lag is annoying although it's way better than my Xoom's. I was just wondering what you guys were hovering at.
I do have an app that turns itself on in my running apps list (it's ESPN's Fantasy Football app) I want to keep the app but it's sort of annoying seeing it pop up there all the time. Is there a way I can force it to stay off?
Click to expand...
Click to collapse
Do you have a widget running for this app? Any app that has a widget on the main screen will automatically run because of said widget.
I personally think thats REALLY low. I'm typically sitting over 400MB free with a couple widgets running and battery monitor in the background as well.
As of this moment I'm showing 367 free. Apps running: Angry birds RIO, Phone, Google Music (with music streaming currently), battery monitor, settings page.
4.0.1 is not memory efficient at all compared to 4.0.2&4.0.3. Not only are the newer builds more efficient with RAM but the size of the ROM on disk is much leaner.
After a reboot and once the dust was settled seems like I have 346 MB of free RAM, something you should try just to see how much you are starting with.
So I'm assuming you're on a build other than 4.0.1? I just tried a reboot and am sitting at 290MB free, I'll monitor it to see how long it takes to get back to the low 100's.
As for the Fantasy Football app, it does NOT have a widget. And apps that HAVE widgets, like Pandora, Evernote, Music, Docs, Soundhound, none of those show up in running OR cached apps.
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
Oftentimes, my phone will lag. I don't have much installed and I go to the running apps to see what is going on. I will always see the settings using 70MB or more of memory. What is the cause of this and is there any way to cure it?
Do optimizations. zipalign, ZRAM or TurboBoost
When you enter settings that's how much is used. When you exit, that will be free again, eventually...
With Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify - if you use paid version, you can also greenify system apps...
bratusm said:
When you enter settings that's how much is used. When you exit, that will be free again, eventually...
With Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify - if you use paid version, you can also greenify system apps...
Click to expand...
Click to collapse
I don't recommend greenifying settings as it will cause lag or problems elsewhere. The reason 70mb is so large is because it is reading from everything on the phone, and so everything is awake and up and running. Like Bratusm says once you close settings and the memory is needed elsewhere it is reallocated with no problems.
HI ALL,
I will root my device , but I want to know how to increase its performance and speed and reduce RAM usage?
and what is the best browser for Android for fast browsing and low memory usage?
Most of the speed increasing and RAM decreasing can be done without root. Replacing Touchwiz with Apex or Nova Launcher is the first step that makes the most difference. Disable most of the bloatware and turn down animations in developer options.
This post probably belongs in the Q&A section, not the software one.
Reduction in RAM usage doesn't necessarily equate to performance boost. Android memory management does a good job of keeping things running smoothly so the goal of debloating should not be to free up RAM. To maximize performance with regards to memory usage with Android what you'll want to do is debloat your device to the point that applications that you'll never use are no longer loading into memory automatically (either as active applications or cached) which will allow other frequently used applications a chance to load into RAM/cache for quick response times. Running memory management software is also counter productive as it will battle against Android's own memory management and kill background applications that you may want cached for quicker response when needed.
Personally I WANT RAM to fill up because if I'm jumping from application to application I don't want to wait for things to load from storage into RAM. I also refrain from cache cleaning frequently because I have a particular routine when I use my device (frequenting particular websites and using particular applications daily) so clearing cache frequently will only force my device to have to re-cache things unnecessarily.
Getting down to the nitty gritty of how to debloat, the approach I took for my device is to work with a few applications; SystemPanelLite Task Manager, Greenify, Boot Manager and Titanium Backup. I would clean boot my device and let it sit for a while (several minutes) to cache applications as it saw fit. I'd then pop into the system panel lite application and look at what was loaded into both active processes and cached. I'd evaluate each entry to determine for myself whether or not I wanted that application to load automatically or not OR NEVER. If the answer was never then I'd use Titanium Backup to freeze the application (of course for each app I'd do my research to see if it was serving an important function). If the answer was that I needed the application but not all of the time then I'd look into Greenifying it and also considered disabling it from starting at boot using boot manager.
I'd do the above iteratively until all I saw in RAM or cached were applications and services that I felt were important. Never during this process did I care how low memory usage was since the goal is to preload as much of the important stuff as possible.
In the end I ended up freezing a ton of Samsung apps, especially after uninstalling applications that relied on their own app store like Hancom.
Of course a quicker way to reduce bloat is to go to a ROM that someone else has debloated and start there as a base. I began my own debloating process early last year though so starting again on a ROM even if it already is debloated to a certain extent doesn't seem worth it for me at this time (but if a lollipop update rolls out and a ROM developer updates to that then I'll surely try it).
Sent from my SM-P900 using Tapatalk
ShadowLea said:
Most of the speed increasing and RAM decreasing can be done without root. Replacing Touchwiz with Apex or Nova Launcher is the first step that makes the most difference. Disable most of the bloatware and turn down animations in developer options.
Click to expand...
Click to collapse
thanks a lot man , I used nove launcher and its v nice , I guess need to root so I can freeze more apps as not all can be disabled using offical rom
muzzy996 said:
This post probably belongs in the Q&A section, not the software one.
Reduction in RAM usage doesn't necessarily equate to performance boost. Android memory management does a good job of keeping things running smoothly so the goal of debloating should not be to free up RAM. To maximize performance with regards to memory usage with Android what you'll want to do is debloat your device to the point that applications that you'll never use are no longer loading into memory automatically (either as active applications or cached) which will allow other frequently used applications a chance to load into RAM/cache for quick response times. Running memory management software is also counter productive as it will battle against Android's own memory management and kill background applications that you may want cached for quicker response when needed.
Personally I WANT RAM to fill up because if I'm jumping from application to application I don't want to wait for things to load from storage into RAM. I also refrain from cache cleaning frequently because I have a particular routine when I use my device (frequenting particular websites and using particular applications daily) so clearing cache frequently will only force my device to have to re-cache things unnecessarily.
Getting down to the nitty gritty of how to debloat, the approach I took for my device is to work with a few applications; SystemPanelLite Task Manager, Greenify, Boot Manager and Titanium Backup. I would clean boot my device and let it sit for a while (several minutes) to cache applications as it saw fit. I'd then pop into the system panel lite application and look at what was loaded into both active processes and cached. I'd evaluate each entry to determine for myself whether or not I wanted that application to load automatically or not OR NEVER. If the answer was never then I'd use Titanium Backup to freeze the application (of course for each app I'd do my research to see if it was serving an important function). If the answer was that I needed the application but not all of the time then I'd look into Greenifying it and also considered disabling it from starting at boot using boot manager.
I'd do the above iteratively until all I saw in RAM or cached were applications and services that I felt were important. Never during this process did I care how low memory usage was since the goal is to preload as much of the important stuff as possible.
In the end I ended up freezing a ton of Samsung apps, especially after uninstalling applications that relied on their own app store like Hancom.
Of course a quicker way to reduce bloat is to go to a ROM that someone else has debloated and start there as a base. I began my own debloating process early last year though so starting again on a ROM even if it already is debloated to a certain extent doesn't seem worth it for me at this time (but if a lollipop update rolls out and a ROM developer updates to that then I'll surely try it).
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Really helpfull man thanks a lot for all the information u shared, am ok with but guess will need to do more research for greenify cuz I didnt use it at all, secondly what office u used after uniinstalling hancom?
I'm currently using Microsoft's Word/Excel Preview apps and have an Office 365 account to enable editing. I've just started (1 month trial) so I haven't really gotten a lot of use out of the software yet.
I can't speak for anyone else but myself but my reason for dropping Hancom was twofold; 1) it did not support the review/commenting features that I needed in Word files and 2) it often required updates at inopportune times. My needs are quite specific, my tablet is a reference and note taking device for meetings and is never used for production type work. As such, I need the ability to take email attachments, open them for review and comment and then send the comments back out as email attachments. The limitations of Hancom when it comes to track changes were a deal breaker for me since I could not see the history of development of reports/documents.
Microsoft's mobile version of Word implements the best support of track changes/comments that I've found to date, so I'm forced to pay the premium of a 365 subscription on this device to get what I need.
muzzy996 said:
I'm currently using Microsoft's Word/Excel Preview apps and have an Office 365 account to enable editing. I've just started (1 month trial) so I haven't really gotten a lot of use out of the software yet.
I can't speak for anyone else but myself but my reason for dropping Hancom was twofold; 1) it did not support the review/commenting features that I needed in Word files and 2) it often required updates at inopportune times. My needs are quite specific, my tablet is a reference and note taking device for meetings and is never used for production type work. As such, I need the ability to take email attachments, open them for review and comment and then send the comments back out as email attachments. The limitations of Hancom when it comes to track changes were a deal breaker for me since I could not see the history of development of reports/documents.
Microsoft's mobile version of Word implements the best support of track changes/comments that I've found to date, so I'm forced to pay the premium of a 365 subscription on this device to get what I need.
Click to expand...
Click to collapse
thanks for reply and sorry for late , hoping the android 5 be great
Install cm12 lollipop ROM. Drastic improvement in browser performance and gaming. For example, Asphalt 8 is extremely slow on stock, even overclocked. On cm12 it runs perfectly with max graphics settings. Unfortunately you lose all the cool touchwiz features like multi window. For me, the performance improvement is enough that it's worth the lost features. I'm anxiously waiting for the official lollipop update.