Develop Bugs

[Q] Total memory less than 768 MB???

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).

[Q] Memory management

Hi Arc Users,
Do you guys encounter low memory after long period of usage? It seems like the memory does not free up after using the phone for a long time. I mainly use the phone for FB, Camera and messaging.
When the phone hits like 50+MB ram or so it starts to slow down and if it goes lower than 40MB my home screen starts to lag and the app icons take a few secs to load every time i return to home screen. I'll usually reboot the phone but its quite a pain considering the boot timing for my phone is rather long, like close to 1 min.
What are the possible solutions? I've heard that advanced task killers are unnecessary for Gingerbread. If thats the case, how do I free up more memory or have better memory management for the Arc?
Am a first time android user, appreciate any advice from you guys
Thanks!

___________________
+1

Root is the solution. Delete apps and services which you do not use.
I haven't any problem either when free ram goes down to 30MB and i don't use a taskiller.

Just what are you doing when you run out of ram? Never did I run out of ram yet. Running ram hungry games will free up more what is needed as I experienced. When I return to homescreen, it takes a while (around 2 secs) because it will free up ram from the game, then load the homescreen launcher from start/scratch.

Same here but my Arc works fine, even with 30-40MB RAM, so it isn't a real problem.
But it would be nice from SE to make 400-450MB of the 512MB RAM available for the user.
Sent from my LT15i using XDA Premium App

Flo95 said:
But it would be nice from SE to make 400-450MB of the 512MB RAM available for the user.
Sent from my LT15i using XDA Premium App
Click to expand...
Click to collapse
What? That is a completely pointless excercise if you understand how ram is handled by the os.
You need to root and remove bloat, check ya settings etc to get better performance. I found letting things constantly access the network was a juice eater, I don't want fb to check every 4 seconds, I update it when I want to read it lol
I use a task manager, but only because I like to see what is running and using resources. I rarely actually kill any apps, just occasionally a few things I rarely use. Even then it fills the space with other stuff.
:edit: sorry flo95, that sounded a bit crappy, no bad attitude was intended.
Sent from my LT15i using XDA App

This is the solution...https://market.android.com/details?id=com.lim.android.automemman&feature=search_result
not a task killer... a memory manager that enhances googles memory management.

mariolouis said:
Just what are you doing when you run out of ram? Never did I run out of ram yet. Running ram hungry games will free up more what is needed as I experienced. When I return to homescreen, it takes a while (around 2 secs) because it will free up ram from the game, then load the homescreen launcher from start/scratch.
Click to expand...
Click to collapse
I do not play games with my Arc. I just used facebook, MSN, Camera and messaging occasionally throughout the day. Medium usage.
It runs smoothly for several days but maybe after a week or two, the RAM starts to get low.
im_iceman said:
This is the solution...
not a task killer... a memory manager that enhances googles memory management.
Click to expand...
Click to collapse
Thanks! Working so far... will monitor after a week or so.

Try a cache cleaner also will free up some space for ya
Sent from my LT15i using XDA Premium App

I use battery guard as a task killer. It comes with a widget where you can see the available amount of ram.
I'm happy about it. Though a lot of people say a task killer doesn't help I have no negative experience using this one... and I never go below 130 ram.
I still think it does help to close tasks that otherwise keep running in the background... But I'm new on android so I could be wrong.

Hey guys
Have you tried this script
http://forum.xda-developers.com/showthread.php?t=1111145
maybe this can help w/o having to install apps or task-killers. Should work on Xperia Arc but I don't guarantee it.

That script seems to do basically the same thing as auto memory manager.. (per my previous post..)..
PS.. I currently have mine set to aggressive.

How do I stop apps auto opening

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

[Q] Low Ram

Is this normal?. my ram is really low and im only running what you can see?
Any advice please:fingers-crossed:

I wouldn't say that's too low. So you can sit back and relax
Sent from my One V using xda app-developers app

oh rite thanks!

Yes show me ur cached process es
Mine is alot more like 144 mb free
Sent from my One V using xda premium

View attachment 1505207
Sent from my One V using xda premium

Sorry for the late reply. I was root/s-off a friends desire for him
here it is.
EDIT:::: I have 0 ram free now!

striped121 said:
Sorry for the late reply. I was root/s-off a friends desire for him
here it is.
EDIT:::: I have 0 ram free now!
Click to expand...
Click to collapse
Reboot, delete some useless apps, close out of your programs more often.. etc
Sent from my HTC One V using xda app-developers app

that's too less mate.. i never have less than 70mb ram
even though i use SwiftKey and whats app
what i use is titanium tweaker app from the market
go to voltage set it to - 150 (for battery)
note set to - 150 only if you're oc to 1024
if higher don't do.. The phone won't respond..
then go to advance/turbocharger lmk
select megaram2
done see the difference
Sent from my One V

dude unless u play games mine always shows 144 mb, remove **** that u dont use
download this from the market
https://play.google.com/store/apps/details?id=com.rs.autorun.pro&hl=en
the paid one is awesome,but there is a free one also!, diavle the startup of junk bloatware and reboot!

4 bucks for a 87KB app? xD
Lowest ram I had was 51MB, and I use Sense 4.1. I would say using task killers help if your one of them people who want to see your ram high. If your device feels sluggish after use, use a task killer, or reboot.
I'm sure CM has that low mem problem though ither way. I saw someone posting bugs about it.
Sent from my HTC One V using Tapatalk 2

Curiousn00b said:
4 bucks for a 87KB app? xD
Lowest ram I had was 51MB, and I use Sense 4.1. I would say using task killers help if your one of them people who want to see your ram high. If your device feels sluggish after use, use a task killer, or reboot.
I'm sure CM has that low mem problem though ither way. I saw someone posting bugs about it.
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
use the free version then!

Suppose ill just ignore it then as my phone is smooth and fast anyhow. just curiious to why really. it's at about 70 now on average.

striped121 said:
Suppose ill just ignore it then as my phone is smooth and fast anyhow. just curiious to why really. it's at about 70 now on average.
Click to expand...
Click to collapse
i said it numerous times... android is NOT windows. your free ram in linux => your system fails to work. your free ram in windows => you can open up more programs until the ram is full.
in linux it is better to have the whole ram full, not free. if you want more infos, you can search on the net.
When an Android app is no longer in use, the system will automatically suspend it in memory - while the app is still technically "open," suspended apps consume no resources (e.g. battery power or processing power) and sit idly in the background until needed again. This has the dual benefit of increasing the general responsiveness of Android devices, since apps don't need to be closed and reopened from scratch each time, but also ensuring background apps don't waste power needlessly
Click to expand...
Click to collapse
and
Android manages the apps stored in memory automatically: when memory is low, the system will begin killing apps and processes that have been inactive for a while, in reverse order since they were last used (i.e. oldest first). This process is designed to be invisible to the user, such that users do not need to manage memory or the killing of apps themselves.[65] However, confusion over Android memory management has resulted in third-party task killers becoming popular on the Google Play store; these third-party task killers are generally regarded as doing more harm than good.
Click to expand...
Click to collapse
source: Wikipedia

1ceb0x said:
i said it numerous times... android is NOT windows. your free ram in linux => your system fails to work. your free ram in windows => you can open up more programs until the ram is full.
in linux it is better to have the whole ram full, not free. if you want more infos, you can search on the net.
and
source: Wikipedia
Click to expand...
Click to collapse
Thanks for giving everyone who isn't aware some knowledge :highfive:Getting tired of these kinds of topics.
"More doesn't always mean better"

1ceb0x said:
i said it numerous times... android is NOT windows. your free ram in linux => your system fails to work. your free ram in windows => you can open up more programs until the ram is full.
in linux it is better to have the whole ram full, not free. if you want more infos, you can search on the net.
and
source: Wikipedia
Click to expand...
Click to collapse
but 1ce keeping them in the memory drains battery also right? so i prefer just remove some bloatware auto start aps

rockstar_26 said:
Thanks for giving everyone who isn't aware some knowledge :highfive:Getting tired of these kinds of topics.
"More doesn't always mean better"
Click to expand...
Click to collapse
if your tired of these kind of topics then simply dont read them.
I Thank you for the info and understand perfectly now as i've never used linux prior to android annd never wanted to.

cybervibin said:
but 1ce keeping them in the memory drains battery also right? so i prefer just remove some bloatware auto start aps
Click to expand...
Click to collapse
wrong. they remain in memory but they will not consume anything. that's what cache memory means.

1ceb0x said:
wrong. they remain in memory but they will not consume anything. that's what cache memory means.
Click to expand...
Click to collapse
I am backig up everything Ice wrote above...
Also if you need auto start manager(free) go check this two https://play.google.com/store/apps/...1bGwsMSwxLDEsImltb2JsaWZlLnRvb2xib3guZnVsbCJd
https://play.google.com/store/apps/...wxLDEsImNvbS5qcnVtbXkubGliZXJ0eS50b29sYm94Il0.
Much more then just auto start managers..enjoy

[Q] RAM is at 2GB of 3GB ??

I have noticed that im using up 2gb of ram. But i have only downloaded a few apps. No games. All the stuff i had before. My old phone was a little over 1gb total. Is this normal. Does the phone uses a lot of ram out of the box. Im thinking of rooting just so i can free up some ram. Not sure if that is possible. Im coming from a galaxy and very happy with this d851 g3.
Anyone having a memory problem ? Issues? What can i do?

Android always runs while using up as much ram as possible. Thats normal, if your phone had 8gb of ram, most likely it would also be using most of it up.

Makes app switching faster.......

All that bloatware runs in the background contributing to a high ram usage

nohcho said:
All that bloatware runs in the background contributing to a high ram usage
Click to expand...
Click to collapse
Not completely true. I disabled most of the T-Mobile and LG crap on this phone and it's still using the same amount of RAM. It's Android's memory management.

I bet if the Android team could go back in time in the early days of system development they would have probably removed the ability to see free ram. So many people get caught up in free ram when the phone is using the available ram to the best of its ability.

Windows does alot of the same as well. Even though if you go into task manager it shows free if you actually look at your system resourses it shows alot of it is taken.

Unused RAM is wasted RAM.

Not sure about the whole 2g for 3gb thing but your system need all the rams it can use to keep your phone running smoothly. If you use ram cleaner (so they are call) you will notice your phone goes through a gitter before it it can pick up again. You look 5 minute later, its like you never clean anything.
and tmobile is surely 3g

Free RAM is wasted RAM.

Android uses RAM differently from say Windows. Android will use as much ram as available and when it needs more, it will free it up as needed. This is normal.

So yea i installed greenify and it made a **** load of a difference because i have like 40 games and a load of other apps. I have less than 1.5 gigs used now. And my phones way smoother and batterylife is good again
Sent from my LG-D851 using XDA Premium 4 mobile app

brolic925t said:
So yea i installed greenify and it made a **** load of a difference because i have like 40 games and a load of other apps. I have less than 1.5 gigs used now. And my phones way smoother and batterylife is good again
Sent from my LG-D851 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't worry you're about to see that battery life drop like a rock. Constantly killing apps will kill your battery fast. Greenify is a nice app if you have a crap phone but your G3 was made the way it is for a reason. What you think is smooth and fast is actually hurting your phone. Don't believe me, Google it and do some research. I do not recommend anyone using any format of task killer or ram optimizer on a phone that is current with the times.

Do I think the phone has issues. yes. When using it the apps don't close when ram is needed. Only fix is a reboot or kill the app but at times that does not work

Jammol said:
Don't worry you're about to see that battery life drop like a rock. Constantly killing apps will kill your battery fast. Greenify is a nice app if you have a crap phone but your G3 was made the way it is for a reason. What you think is smooth and fast is actually hurting your phone. Don't believe me, Google it and do some research. I do not recommend anyone using any format of task killer or ram optimizer on a phone that is current with the times.
Click to expand...
Click to collapse
Don't worry Jammol doesn't know what he is talking about. Greenify doesn't hurt battery life and performance like a task killer because isn't a task killer. It is completely different. I agree that task killers should be renamed to battery/phone performance killers but Greenify is very different.
First of all it requires your phone to be rooted. Assuming that it is, it uses special permissions from the rooted device to essentially freeze the app unless it is opened by the user. For example, I use facebook but only casually. I look at it once every other day or so but have noticed that the push notifications and messenger uses a lot of battery because it does a partial wake everytime it pushes a update which activates the internet and cpu.
The solution is to "Greenify" the app. The app still loads normally when I open it up although, because it is not in the ram, it likely takes slightly longer to load. Once it is opened, I can use it like normal and I get push notifications again until my phone's screen goes off. Once the screen goes off, facebook and all the apps that I "Greenify" are flushed from the memory and are banned/essentially frozen until I launch the respective app again. The only drawback to this is that you essentially never get push notifications for the apps but it saves a lot of battery if you pick the apps that you don't care much about/rarely use.
So greenify does work really well. Today my phone had 17% left. I it had 16+ hours of battery time total. I got 4.25 hours of SOT with sync on (with 3 email accounts getting push notifications plus other apps), GPS high accuracy, LG health automatically recording my exercise, and 1 hour of navigation with Waze. Basically I used my phone how I wanted and didn't micromanage my battery usage throughout the day at all.
I used 3 battery saving tools. 1. ART 2. Greenify and 3. Custom Kernel V002 from KAsp3rd. These three are very powerful together.
I hope that helps someone!

ART

CAP3r5 said:
Don't worry Jammol doesn't know what he is talking about. Greenify doesn't hurt battery life and performance like a task killer because isn't a task killer. It is completely different. I agree that task killers should be renamed to battery/phone performance killers but Greenify is very different.
First of all it requires your phone to be rooted. Assuming that it is, it uses special permissions from the rooted device to essentially freeze the app unless it is opened by the user. For example, I use facebook but only casually. I look at it once every other day or so but have noticed that the push notifications and messenger uses a lot of battery because it does a partial wake everytime it pushes a update which activates the internet and cpu.
The solution is to "Greenify" the app. The app still loads normally when I open it up although, because it is not in the ram, it likely takes slightly longer to load. Once it is opened, I can use it like normal and I get push notifications again until my phone's screen goes off. Once the screen goes off, facebook and all the apps that I "Greenify" are flushed from the memory and are banned/essentially frozen until I launch the respective app again. The only drawback to this is that you essentially never get push notifications for the apps but it saves a lot of battery if you pick the apps that you don't care much about/rarely use.
So greenify does work really well. Today my phone had 17% left. I it had 16+ hours of battery time total. I got 4.25 hours of SOT with sync on (with 3 email accounts getting push notifications plus other apps), GPS high accuracy, LG health automatically recording my exercise, and 1 hour of navigation with Waze. Basically I used my phone how I wanted and didn't micromanage my battery usage throughout the day at all.
I used 3 battery saving tools. 1. ART 2. Greenify and 3. Custom Kernel V002 from KAsp3rd. These three are very powerful together.
I hope that helps someone!
Click to expand...
Click to collapse
Out of curiosity, how are you using art with xposed? Greenify uses the xposed framework.
Sent from my LG-D851 using XDA Free mobile app

Harmtan2 said:
Out of curiosity, how are you using art with xposed? Greenify uses the xposed framework.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I am not using xposed. Greenify works just fine for me without xposed. If you want some of the more advanced and experimental features, you need xposed but the basic functionality does not require it..

CAP3r5 said:
I am not using xposed. Greenify works just fine for me without xposed. If you want some of the more advanced and experimental features, you need xposed but the basic functionality does not require it..
Click to expand...
Click to collapse
Aww that man's sense. I want to ruin art, I just don't want to give up my xposed features lol.
Sent from my LG-D851 using XDA Free mobile app

Harmtan2 said:
Aww that man's sense. I want to ruin art, I just don't want to give up my xposed features lol.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
I know what you mean! This is just the latest skirmish in the never ending war between features and battery/performance. I can't wait for Android L to come out because this particular battle will end (xposed will support android L which uses ART exclusively) but the war will rage on..