Database Users

What the **** is up with the ram?

On the nexus one there is about 500 mb of ram. Whenever I put my phone on and I kill all my tasks, I only have 120 mb. This is not the biggest problem because after about 30 minutes of using the phone, no matter if I kill all the apps, the ram goes to 70mb - 79mb.

Android 2.2 should fix this.
Or you can use a custom ROM such as cyanogen, with which i have over 230MB free RAM after closing apps

There are already a million and now one threads on this subject, search and you shall find all you could ever care to know about the subject.

You should be using the RAM, not freeing it. The only way you lose battery is if the Application/Widget is downloading or using the CPU/GPU. On your PC, do you go to task manager and kill apps every time?

I know it's a hard habit to kick coming from a G1 where it seemed necessary. But on a Nexus, you really don't need to. The only times I have to use it are when an application hangs.

What the **** is up with everyone not wanting the memory in their phones/computers to be used? That is what it's for! If its not being used it is going to waste.
If you guys are using task managers you have failed.

lol chillout!
People are obviously fine with it and welcome not to moan on the internet to people about not being able to use it.
Install a custom ROM if you want to dry your tears about not being able to use the extra RAM.

mets3214 said:
On the nexus one there is about 500 mb of ram. Whenever I put my phone on and I kill all my tasks, I only have 120 mb. This is not the biggest problem because after about 30 minutes of using the phone, no matter if I kill all the apps, the ram goes to 70mb - 79mb.
Click to expand...
Click to collapse
Killing apps is 100% unnecessary on the Nexus One.
It actually wastes MORE power to kill apps and have them restart all the time, than it does to just leave them alone.
For the next week, uninstall all your task killer apps.
Then tell us how it went.

Ram goblins got to your ram, oh noes!

I'll answer his question. currently the nexus one only has half of the 512mb of RAM freed up, so you only have 256 mb right now. the next update is freeing up the other half.

RogerPodacter said:
I'll answer his question. currently the nexus one only has half of the 512mb of RAM freed up, so you only have 256 mb right now. the next update is freeing up the other half.
Click to expand...
Click to collapse
Sorry, you're right we didn't really directly answer his question I guess. But the point is, people shouldn't be looking at the free memory measurements anymore. Anything that isn't being used by applications will be used by the operating system for caching and other such things (this is a good thing). As soon as another applications starts up and needs that space, the kernel will give it up. Free memory doesn't use less power than memory that is in use by a sleeping process.
While you are correct that not all of the current memory of the device is addressable with the current kernel, when this limitation is removed in the next update (assuming it will be) it still wont solve the OP's problem. All it is going to mean is that even more memory will be taken up as cache space and buffers by the kernel and applications will be closed down even later so you'll still see a pretty small amount of "free" memory. If close to half of the RAM is going completely unused, then that's a lost opportunity by the kernel to cache or prefetch something.
Don't use task managers. They aren't needed and provide nothing. All they do is give fodder to the Steve Jobs' of the world that claim you need to manually micro manage memory on android devices as evidence by the number of people that use them.

Nerd rage much?

So just to clarify, apps don't really "run" in the background, they are just more readily available if they have ram dedicated to them? I'd rather not use a task manager but if it saves any of this pathetic battery I would sacrifice some performance...

DMaverick50 said:
So just to clarify, apps don't really "run" in the background, they are just more readily available if they have ram dedicated to them? I'd rather not use a task manager but if it saves any of this pathetic battery I would sacrifice some performance...
Click to expand...
Click to collapse
The only thing task managers do is kill your battery. If you find that your phone is sluggish , doesn't respond well etc, uninstall some bad apps. Some apps aren't coded very well and remain active all the time killing your battery. Having an app checking all the time if another app is killing your battery is also killing your battery.
Bottom line: Don't use a task killer unless you find it absolutely neccesary to keep your phone running at decent speed.

DMaverick50 said:
So just to clarify, apps don't really "run" in the background, they are just more readily available if they have ram dedicated to them? I'd rather not use a task manager but if it saves any of this pathetic battery I would sacrifice some performance...
Click to expand...
Click to collapse
Look at the link in my signature, it'll explain how the android system manages programs.

V6 Supercharger

So do you guys use it and what does it exactly do? And also what does 3g turbocharger and kick ass kernel tweak do?

Basically everytime the memory drops below the thresholds set by v6, the system will start killing of apps running in the background which frees up memory that you most probably aren't using, Im currently on the aggressive settings so everytime my memory drops below 150mb the system starts killing apps. Its basically just tweaking the internal task killer to be slightly more aggressive. It also locks the launcher so the system cannot kill it if the memory drops too low.
The 3g tweaks, I think adjust or add some settings to the build.prop which supposedly make it faster although I haven't noticed much difference with that and the kernel tweaks I'm not too sure where the changes are made but again I don't see a great change from it. Definitely recommend v6 supercharger though.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
Basically everytime the memory drops below the thresholds set by v6, the system will start killing of apps running in the background which frees up memory that you most probably aren't using, Im currently on the aggressive settings so everytime my memory drops below 150mb the system starts killing apps.
Click to expand...
Click to collapse
Great. Let's take 150MiB of RAM and then don't do anything useful with it. Processes aren't supposed to be killed unless you actually run out of memory.
Scratch0805 said:
It also locks the launcher so the system cannot kill it if the memory drops too low.
Click to expand...
Click to collapse
That seems innocent, but it won't help you if the launcher has a memory leak. If the launcher kept getting killed, it was telling you that your low memory thresholds are too high. Under normal circumstances, the launcher won't get killed. But if it grows too much, it'll get killed and the OS won't crash.
When you force close an application through the application manager, it shows you a warning. There's a reason for that (exactly what it says). And since Android 2.2, the framework can take care of itself just fine. No need for any 3rd party task killers.

Lol..... Thought you'd have something to say on it, actually mate the way my phone is usually setup there is nothing running in the background to kill anyway, thanks to autostarts I only have apps running that I need and make sure that I close things properly after use, so it really doesn't matter which settings I use whether they be low such as 30mb before it starts killing the first lot of empty apps or high such as 150mb as my setup rarely drops below because there is only the bare minimum running in the first place.
Sent from my HTC Wildfire using xda premium

Allright, it's not that RAM would slowly wear and tear by using it but at least you're not buying that it's better for performance. And I just wonder how these apps are made, as a thought experiment to figure out the mindset of whoever wrote this task killer.
...So let's make an app which looks real cool and doesn't do anything useful in particular! Wait, no one would download that! Hmm... Oh, I know! Let's call it "V6 Supercharger"! Yeah, that sounds awesome! Now people will download it for sure! It's the coolest thing since sliced bread!
It's the same with those programs like "Registry Booster". How did that happen? Someone must've woke up one day, turned on his PC, started poking in the registry, saw lots of keys which aren't really strictly necessary but are there anyway and thought like "Hmm, what if I made a program which removes all these unneeded keys? MS-Windows would be ZOMG faster!!111eleventyone". Then made it look real slick with a custom skin and a speedometer showing progress and say at the end that the registry has been "boosted". And since this guy is such a nice fellow, he threw in some extra free toolbars into the mix as well. Users always appreciate having more toolbars to click on and agreements to ignore.
Ok, I'll stop ranting now. Enjoy your week

Try explaining that to the dev who created it here. Honestly, it would be better, because, I am pretty sure most members here are not as technically inclined as you.:
http://forum.xda-developers.com/showthread.php?t=991276

You're just setting him up so I can tear him apart... aren't you?
The poor bastard doesn't even know what it is... he thinks it's a task killer app... heh

No, I would like him to discuss all the technical aspects with you. Because, clearly, he's wasting his effort as a developer here educating non-technical people like me, and the majority here on the Wildfire Forums.
And before you accuse me of trying to set people up, I can assure you I have nothing against you / your script or anything. Rather, I have used your script, and came away impressed with it.

I know you you weren't doing anything like that... I'm always putting down these clowns that think that suffocating the phone is good... idiots lol
Like I say, what the hell good is phone if you can't make a call because of some crap hogging the ram?
Besides, I doubt very much he has any technical skills at all... like I said before, he doesn't even know what it is so he's not very techinical

dud3me said:
what does it exactly do?
Click to expand...
Click to collapse
It makes you feel good.
And I definitely noticed a 0.00001ms speed difference when opening apps.

Another liar

zeppelinrox said:
Another liar
Click to expand...
Click to collapse
Yeah lol. Most people in this forum are wannabe developers who know **** about developing but they like to act like they do. Apart from few people who actually know stuff and the others like me who acknowledge the fact that we don't know anything

Fact is, those who know they don't know learn more than those that think they know it all
Less than a year ago, I knew 0 about android.
And when I started the supercharger script, I knew nothing about linux scripting.
Just started off with a few commands and everytime I wanted to try something new or add something... I googled it up.
And I'm still figuring it out.
For example, I set my 256mb device to have 25mb free with the number I use in slot 3.
So whatever memory tool I use will show I have 25 or 30mb free... great - that's what I want
But when I was doing up the recent update and enhanced the Fast Engine Flush, I wanted to show before and after using the "free" command.
To my surprise, system tuner shows that I have 30mb free while the free command shows I have only 5mb free!
So what's that mean? Why that difference of 25mb?
It means that all that "free ram" is actually being used for cache.
And it's giving me speed
So to those that think it's great to have ram clogged with apps when the system is starving for space to use for cache...
BOOYA!

Really have trouble using your scripts and I think after enabling 3gturbotweak thing my 2g data isn't working haven't tried 3g.

I can't recall it affecting 2g... so I assume 2g used to work (I don't get 2g - it's unavailable)
But if you unturbocharge, the 2g/3g goes back to normal, no?

zeppelinrox said:
I can't recall it affecting 2g... so I assume 2g used to work (I don't get 2g - it's unavailable)
But if you unturbocharge, the 2g/3g goes back to normal, no?
Click to expand...
Click to collapse
Well I had to format system data and cache and wiped everything and now it's working again so I'm not completely sure if it was the turbocharge thing.

The idea that you can magically "supercharge" your OS by freeing up memory is fundamentally flawed.
what the hell good is phone if you can't make a call because of some crap hogging the ram
Click to expand...
Click to collapse
If this is really a problem on your phone, you're doing it wrong. I haven't done anything to free up ram and the amount of ram available on my wildfire is currently 108,48MiB. I start 10 random apps, Angry Birds, and Angry Birds Rio. 40,68MiB still free. I start Angry Birds Seasons and end up with 49,66MiB free and 9 apps died, including the first angry birds. Running out of ram is in general not a failure mode of Android and at no point was I unable to place a call. I close the 2 remaining open instances of Angry Birds the normal back-button way, 147,68MiB free.
I'm always putting down these clowns that think that suffocating the phone is good... idiots lol
Click to expand...
Click to collapse
I just wanted to quote that.
And when I started the supercharger script, I knew nothing about linux scripting.
Just started off with a few commands and everytime I wanted to try something new or add something... I googled it up.
Click to expand...
Click to collapse
That's exactly the impression I had. Now take it from someone who has run Linux both embedded and on his desktop for the past 12 years. Your app doesn't improve anything, and I'd be glad to be proven wrong because you would've actually made a discovery we can use to improve Android and Linux with. From your post I understand it you change vm kernel parameters such that the oom killer is invoked sooner. This is actually detrimental to the stability of the OS, the oom killer is only meant to be invoked as a _last_resort_. The Android framework has its own means to free up memory, including calling onLowMemory in any application and doing a gc run. This does not cause instability and is completely transparent to the user. I've only ever had to manually kill applications in a broken state and others for debugging purposes, which is why the Force Close button exists.
It means that all that "free ram" is actually being used for cache.
And it's giving me speed
Click to expand...
Click to collapse
If the output looks anything like this:
Code:
total used free shared buffers cached
Mem: 3456 3325 131 0 10 93
-/+ buffers/cache: 3221 235
Then you've just never bothered to look. You can clearly see in the second line it makes a calculation for you which is exactly what it says in the leftmost column. And of course completely disregard the fact that cached pages are invalidated on a write (marked dirty) and reads from an mtd are really fast already anyway.
So to those that think it's great to have ram clogged with apps when the system is starving for space to use for cache
Click to expand...
Click to collapse
This is not how it works! For starters, ram cannot be "clogged". A drain pipe can be clogged but ram is made of digital circuitry, not plumbing. And second, there is no resource starvation in the page cache. It's just an old optimisation to keep data pages in memory for longer to serve repeated reads and give them back whenever they're needed for something else. More apps in ram can actually mean less reads are necessary because the data is already there (especially if you tend to switch between recent apps). Since Android 3.0, application developers are encouraged to use Loaders which cause filesystem I/O to be performed on a background thread. And applications which actually use the available ram always trump applications designed to use as little ram possible in performance. Between a collection of loaded objects and a cached filesystem, the collection always wins. You have 256 to 512 MiB of RAM in a typical Android device. The average application is 18 to 30 MiB. It can manage. Especially when you consider the fact that the UI only shows 1 task at a time and pressing the back button usually destroys the activity you were in. The gc takes care of its remains.
Now here's something which will actually improve write speeds on /data: Open up settings, applications, manage applications. Sort by size. Remove the biggest apps you don't need and move the rest to SD if you can (you can use "pm setInstallLocation 2" as root to move non-froyo-aware apps to SD). I've been using the market a lot lately so I just removed aDosBox, Albert Heijn, PocketCloud, Pulse and moved Dolphin Browser to SD which meant 47.25MiB free on /data. On a 175MiB partition, 30% of it is about 52MiB so I'd try to keep the available space around 50MiB. If your phone is low on storage, doing this will perceivably improve performance.

dud3me said:
Well I had to format system data and cache and wiped everything and now it's working again so I'm not completely sure if it was the turbocharge thing.
Click to expand...
Click to collapse
Same thing happened to me, but every time i turned 3g on the phone rebooted and i got stuck in a bootloop, i had to use the ruu update to restore phone.
I would stay away from the network tweaks. It doesnt improve speed anyway.
Sent from my HTC Wildfire using xda premium

henkdv said:
The idea that you can magically "supercharge" your OS by freeing up memory is fundamentally flawed.If this is really a problem on your phone, you're doing it wrong. I haven't done anything to free up ram and the amount of ram available on my wildfire is currently 108,48MiB. I start 10 random apps, Angry Birds, and Angry Birds Rio. 40,68MiB still free. I start Angry Birds Seasons and end up with 49,66MiB free and 9 apps died, including the first angry birds. Running out of ram is in general not a failure mode of Android and at no point was I unable to place a call. I close the 2 remaining open instances of Angry Birds the normal back-button way, 147,68MiB free.
Click to expand...
Click to collapse
All that you said is very informative.
What are your minfrees?
Set them to something like 6, 12, 16, 18, 26, 30.
Run a bunch of apps...
See how great it runs then
Fact of the matter is, user's with 1GB ram devices notice a real improvement.
Not placebo.
Pressing the home or back button has an instant effect without hesitation - which indeed happens on stock roms.
Yes in theory I'm sure it all makes sense and I apologize for using layman's terms such as "clogging".
An android phone is not a Linux PC so I believe it's not a great idea to configure it like it is a Linux PC.
They have difference purposes.
Anyway, in theory, a bumble bee can't fly - but it does.

WTF with the ram

i can only open about 3-4 app before my ram is full and its forcing to closing app . seriously ? wtf is this .
i feel like this phone is worse than n95 .
if i open a web page one youtube link and i still have in memory my message app it will start closing app and sometime it even close the Touch wiz widget so they have to re appear and load for 4 second . i cant believe they only putted 1gb of ram with all there touchwiz bloarware.

Ram issues
Check what apps are running on the background, i would check primarily things you log into that are always logged in like FB, Gtalk, Skype. although even with all those running you shouldnt have issues, maybe try doing a cache and dalvik cache wipe reboot and check changes.
MY BEST FIX is rooting, flashing an AOSP based rom that normally for me they use 350 to 400mb on a normal basis instead of 550-600mb in a sammy based rom.

mine is usally 800-1g and im constantly clearing memory. I dont get it either.

1slow4G said:
mine is usally 800-1g and im constantly clearing memory. I dont get it either.
Click to expand...
Click to collapse
S3 has a horrible memory management.
1 gb ram ain't enough for the beast.
Launcher redraw on a Top end phone is an Epic fail.

Selina40Kyle said:
S3 has a horrible memory management.
1 gb ram ain't enough for the beast.
Launcher redraw on a Top end phone is an Epic fail.
Click to expand...
Click to collapse
I agree, I just opened every app i have and went up to 1.26gb.. and when i have no apps open it jumps from 800-1gb on its own.. so i guess its all in the system that takes up most of the space

Selina40Kyle said:
S3 has a horrible memory management.
1 gb ram ain't enough for the beast.
Launcher redraw on a Top end phone is an Epic fail.
Click to expand...
Click to collapse
Jeez 1gb is more than enough

Problem is with the Samsung bloatware. Kies, Remote Controls and all those other services. Delete kiesexe and freeze the Samsung crap inc SVoice..
I see no need to sync to Samsung and Google. The Google services are enough.. The Samsung store is only worth unfreezing for those free offers. The four tracking services ain't needed etc I use Avast to do that etc.
Getting 285M free apx after bootup, same as ICS, on 4.1.2 now. 12 widgets, FB, G+, Fancy widgets, Jorte etc
Also make sure not to run supercharger. It kills multitasking!

Disable all the Bloatware or freeze it using link2sd.
(all share, talk back, s-voice)
Still sitting between 540mb and 630mb maximum
Sent from my GT-I9300 using xda app-developers app

Kojaes
My 2gb i747m really makes use of the extra ram. It not only can handle 50 background apps with stock rom as apposed to 15-20 for the 1gb version (assuming there is enough ram), but it will boot with about 1.6-1.7gb available, about 700mb used, and 1gb free, and will use memory up to about 200mb free before killing apps to make room for new apps. Bottom line, it multitasks like a S.O.B. My opinion based on 2.5 years Android experience...is that 2gb ram helps big time...especially if you do not optimize your system.
If I had the 1gb version, I would consider a lighter rom as some have mentioned, but also the V6 Supercharger app with specific settings to allow maximum multitasking while remaining stable...which might take some experimenting. I would install Titanium Backup Pro and freeze as many non needed apps to prevent them from loading at boot and using up precious ram. Also, for some apps, I use AutoRuns to prevent them from loading at boot time.
Also remember...that some apps will stay in RAM when it's plentiful. But other apps are programed to allow Android to kill them after a certain length of idle time when they haven't been used.

Ram management is fine on the S3.
If you are not happy with it use a task killer, custom rom/kernel and/or supercharger v6 script.
Also if your ram<100 then you should start making complaints.
My free ram is at 120mb-160mb and i'm happy,no lags,no slowdowns,nothing at all.
Android preloads apps in memmory in order to open faster when we launch them.
Free ram really is wasted ram...it cancels multitasking and if you've bough a 600$ phone and can't multitask with it then you're worth of your fate.

nfsmw_gr said:
Ram management is fine on the S3.
If you are not happy with it use a task killer, custom rom/kernel and/or supercharger v6 script.
Also if your ram<100 then you should start making complaints.
My free ram is at 120mb-160mb and i'm happy,no lags,no slowdowns,nothing at all.
Android preloads apps in memmory in order to open faster when we launch them.
Free ram really is wasted ram...it cancels multitasking and if you've bough a 600$ phone and can't multitask with it then you're worth of your fate.
Click to expand...
Click to collapse
The fact that an user has to get task killer and manage memory by him own: FAIL!
I know android pre loads stuff in memory, but it got the priority all wrong.
Why does it keep killing msging, phone and the GODDAMN launcher .
While it never kils the stupid stuff like "Google Book mark Sync", unless you freeze it.
There's no denying that 1gb has crippled S3 badly.
You can claim "Free ram is wasted ram" and throw down links, but at the end of the day it is giving me a bad experience.
Case in point:
1) Launcher Redraw:
Two points to it:
->Bad priority (I'm not sure if it's either a Samsung fault or Android; OOM 6 isn't the way to go).
-> Less ram.
The fact that browsing through play store for 15 mins and then hitting Home button results in launcher redraw is pathetic.
Less ram is the culprit( atleast one of the).
On such an expensive device this is just EPIC FAIL.
Sure we can do Super recharge and try removing the bloatware, but these are quick fixes and doesn't get rid of the main problem.
Not to mention not every one finds all this stuff easy.
The fact that you have to do tweaking on the 'supposedly greatest android phone' to make it work smoothly is an EPIC FAIL.
Custom Roms for an device as expensive as S3, should be there to enhance functionality and increase features. Not to make it works the way it should have out of the box.
2) Sh**ty Multitasking:
Trust me, my iPod touch does better multi tasking that S3 for day to day experience. (I am not an apple troll, btw)
And it doesn't even have a true multitasking and the specs are no where near S3.
When I pause a game, and resume it after an hour it starts from exactly same place . Try that with S3.
Try to use your phone when many apps are getting updated and notification bar is constantly changing.
It'll lag the hell out.
There's no defending to these points.
This is where Apple excels , by giving user everything perfect from out of the box.
Sure you can't do much, but what ever you can, you do it smoothly.
What makes me sad is that Samsung is so close to it, yet they screwed the experience.
And I'm not even going to talk about Contacts and Phone apps.

nfsmw_gr said:
Ram management is fine on the S3.
If you are not happy with it use a task killer, custom rom/kernel and/or supercharger v6 script.
Also if your ram<100 then you should start making complaints.
My free ram is at 120mb-160mb and i'm happy,no lags,no slowdowns,nothing at all.
Android preloads apps in memmory in order to open faster when we launch them.
Free ram really is wasted ram...it cancels multitasking and if you've bough a 600$ phone and can't multitask with it then you're worth of your fate.
Click to expand...
Click to collapse
Sorry but this is complete and utter drivel. Stop quoting websites and Google and start wising up.
If you have a game that needs to run and it uses 100mb and the phone has no free ram it kills something else.
This would be fine if the phone loaded the apps quickly but it doesn't.
Custom ROMs do not fix the lack of ram and neither do any of the memory management scripts.
My phone has around 200mb to 300mb though and it still loads and reloads phone and messaging and browser randomly.
Sgs3 is useless at memory management and anyone who says otherwise is living in a dreamland.
No lags and slowdowns is just blatantly not true as your messaging app and phone app will frequently take up to two seconds to load if you are using any Samsung ROM.

biffsmash said:
Sorry but this is complete and utter drivel. Stop quoting websites and Google and start wising up.
If you have a game that needs to run and it uses 100mb and the phone has no free ram it kills something else.
This would be fine if the phone loaded the apps quickly but it doesn't.
Custom ROMs do not fix the lack of ram and neither do any of the memory management scripts.
My phone has around 200mb to 300mb though and it still loads and reloads phone and messaging and browser randomly.
Sgs3 is useless at memory management and anyone who says otherwise is living in a dreamland.
No lags and slowdowns is just blatantly not true as your messaging app and phone app will frequently take up to two seconds to load if you are using any Samsung ROM.
Click to expand...
Click to collapse
True that.
I have no idea what is stored for 500-600Mb ram if not the important things like Phone, Msg and Launcher.
Useless stuff.

It is just marketing and business politics, Samsung knew that 1GB is not at all future proof but that is exactly what they need so they can sell the Note 2 and the i9305.
And still they sold over 30M i9300 devices.
eggman89 said:
True that.
I have no idea what is stored for 500-600Mb ram if not the important things like Phone, Msg and Launcher.
Useless stuff.
Click to expand...
Click to collapse
Man, Android loads that stuff itself based on usage, OOM settings and Minfree values. The other stuff is services that need to run full time so that Kies sync, Location and other Samsung bloat that is really not doing anything most of the time.

Ya I know.
I wonder how can the most important thing, launcher, has an OOM of 6.
Stupid really.
Is it a fault of Android or Samsung messed it up.
In all the galaxy nexus videos I've never seen launcher redraws.
So maybe Samsung messed up for whatever reason.
Sent from my Samsung Galaxy S3

"Free ram is wasted ram"
Click to expand...
Click to collapse
that remark has been misused greatly by people that can't code for ass and fail at memory optimisation.
It was originally in reference to the Superfetch feature in Vista/7 storing frequently accessed data in ram for faster application startup. It wasn't meant to be applied to applications that use huge amounts of memory for no good reason.
much of Androids poor memory management is Java related, who knows, maybe Google will get a clue and dump the Dalvik VM eventually for a native operating system.

Use aokp or cm 10
Sent from my GT-I9300 using Tapatalk 2

Diaze said:
Use aokp or cm 10
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
For many of us, camera is an important thing.

aakarani said:
Disable all the Bloatware or freeze it using link2sd.
(all share, talk back, s-voice)
Still sitting between 540mb and 630mb maximum
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Is it in the app store ?
Is there any way to freeze samsung permanently without root ?
does link2sd need root to work ?
is advance task killer enough to kill all samsung bloatware ?

Kojaes said:
Is it in the app store ?
Is there any way to freeze samsung permanently without root ?
does link2sd need root to work ?
Click to expand...
Click to collapse
1) Yes.
2) Yes. You can go to "manage apps", select the applications. There will be an option called "Disable". No need for any app.
3) See above

What's your idle ram usage?

See title. Feel like the ram usage on my note 4 is high even when "idle". Please see attached image for details.
Thanks in advance for any feedback.
PS any tips on how to free up ram would be appreciated.

research47 said:
See title. Feel like the ram usage on my note 4 is high even when "idle". Please see attached image for details.
Thanks in advance for any feedback.
PS any tips on how to free up ram would be appreciated.
Click to expand...
Click to collapse
Mine is using 1.77GB. Using Dynamic Kat ROM.

research47 said:
See title. Feel like the ram usage on my note 4 is high even when "idle". Please see attached image for details.
Thanks in advance for any feedback.
PS any tips on how to free up ram would be appreciated.
Click to expand...
Click to collapse
I read on these devices it's supposed to be high. Sounds counter intuitive, but it allows quick access to ram or something along those lines. A quick Google search should help you out.
Sent from my SM-N910T using XDA Free mobile app

Mine is 2.38.
Btw, this is mine without clearing anything, I ran all my normal apps and kept them in memory. Sure, I can get low memory if I clear my recently used apps, but that is not reality.

unused ram is wasted ram so you don't have to worry about it

Stock rooted. 1.56gb idle

Thanks for all the reply. Thought there was something wrong with my device.

I'm on stock rom and I've debloated my device my self. I deleted apps and services, turned off other things that I couldn't delete. My RAM usually sits between 1.16Gb to 1.42Gb.

worrying about idle ram is like worrying about benchmarks...
both mean nothing in a normally functioning phone..

I just posted this answer on reddit, but I guess I will try and spread the word a little more so that these posts stop coming up.
Android uses the Linux kernel, in the world of Linux/ Unix for those that do not know.... Unused RAM is wasted RAM. You phone will remove stuff from RAM if its getting to low on free space.

Colnart said:
unused ram is wasted ram so you don't have to worry about it
Click to expand...
Click to collapse
Yep. If that bar isn't sitting at 2.4 to 2.7, you're not using it enough. The entirety of the RAM is getting refreshed every cycle regardless of whether or not it's being used.
dabbill said:
I just posted this answer on reddit, but I guess I will try and spread the word a little more so that these posts stop coming up.
Android uses the Linux kernel, in the world of Linux/ Unix for those that do not know.... Unused RAM is wasted RAM. You phone will remove stuff from RAM if its getting to low on free space.
Click to expand...
Click to collapse
This is true of any modern OS. Even Windows Vista or newer, which will cache commonly used apps in RAM to allow for faster app starts.

ATnTdude said:
Yep. If that bar isn't sitting at 2.4 to 2.7, you're not using it enough. The entirety of the RAM is getting refreshed every cycle regardless of whether or not it's being used.
This is true of any modern OS. Even Windows Vista or newer, which will cache commonly used apps in RAM to allow for faster app starts.
Click to expand...
Click to collapse
I would agree, that Vista and newer has gotten better, but I would still not consider them any where near as good as Linux / Unix.

[Q] Opening task switcher takes very long (2-4 seconds) on 5.0 Lollipop SM-G900F

I flashed the polish Android 5.0 lollipop on my SM-G900F Galaxy S5. I have the latest xxxBNL9 update. When i hit the task switcher (left) button it takes very long to minimize the screen and open the task switcher. Typically it takes 2-3 seconds. When i do it repetitively it goes quicker. I've already set the "transition animation scale" to off (or 0.5x) in "developer options". Frequently closing all apps also doesn't help.
Please help me. I multitask a lot and this delay is very annoying.

Unfortunately... this is android's fault, it is also experienced by some Nexus Roms.

trettet said:
Unfortunately... this is android's fault, it is also experienced by some Nexus Roms.
Click to expand...
Click to collapse
Well that surprises me. I thought it was the bulky touchwiz for sure. I guess there's nothinh to be done but wait for Google to fix it. Thank you for the information, could you provide a link for anyone else who has the same question?

pizzaman79 said:
Well that surprises me. I thought it was the bulky touchwiz for sure. I guess there's nothinh to be done but wait for Google to fix it. Thank you for the information, could you provide a link for anyone else who has the same question?
Click to expand...
Click to collapse
I couldn't particularly find one on xda, but I've found lots of complaints on reddit..on Nexus and Android subs...just look it up..
Sent from my SM-G900F using XDA Free mobile app

Agreed.
It was faster on 4.4.

There is a memory leak in 5.0 and even 5.0.1-2 that if you keep the phone on more than 2 days running the system eats up the RAM.
Was noted and linked to in the S5 firmware thread.

lynxblaine said:
There is a memory leak in 5.0 and even 5.0.1-2 that if you keep the phone on more than 2 days running the system eats up the RAM.
Was noted and linked to in the S5 firmware thread.
Click to expand...
Click to collapse
Touchwiz is a bit of a memory leak on itself, but i think the memory leak doesn't just affect nexus phones, but also the Galaxy S5. When i look in my memory manager, with only a few small open apps (totalling less than 200mb) my memory is almost full, 1.4 /1.67gb used.
I don't know if that's the actual cause of the delay on opening the memory manager. It might well be, because with more memory it can keep the task switcher open/active longer. The times when there is a delay are probably when the task switcher app was closed because of low memory. When you open it several times, it goes much faster.
Note: I cleared my cache partition after a failed root attempt and reflashed the stock rom (without doing a factory reset). That helped a bit. It went from 2-4 seconds to 1-3 seconds to open the task switcher. It helped, but it's not a permanent fix.

The only temporary workaround as of yet is to reboot the phone regularly, like every 2 days.

2gb is really not enough for this phone... that's why we are seing a lag free note 3 touchwiz rom because it has 3 gb of ram.
Sent from my SM-G900F using XDA Free mobile app

What you talking is nonsense. If 2 are gigabytes of RAM too little why are then 200 to 300 megabytes always free? If you have more than that it is useless. Why would anyone want to have a lot of RAM just sitting there and does nothing. Eats more battery, literally taking space in phone but does nothing.
Sent from my SM-G900F

AlwaysAndroid said:
What you talking is nonsense. If 2 are gigabytes of RAM too little why are then 200 to 300 megabytes always free? If you have more than that it is useless. Why would anyone want to have a lot of RAM just sitting there and does nothing. Eats more battery, literally taking space in phone but does nothing.
Sent from my SM-G900F
Click to expand...
Click to collapse
Having 200-300 MB of ram means yoh have too much crap running, i have 600ish free right now, and as far as i know having more ram would not affect battery life, nlt sure where you got that from.
Sent from my SM-G900A using Tapatalk

Rakuu said:
Having 200-300 MB of ram means yoh have too much crap running, i have 600ish free right now, and as far as i know having more ram would not affect battery life, nlt sure where you got that from.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Of course it affects battery life because phone could have less RAM in total (physically less) which needs less juice. Less RAM needs less physical space and battery can be bigger. So again, if you have a lot free RAM just sitting there, it does nothing and I don`t know which smart ass even started comparing ROM optimization and free RAM.

AlwaysAndroid said:
Of course it affects battery life because phone could have less RAM in total (physically less) which needs less juice. Less RAM needs less physical space and battery can be bigger. So again, if you have a lot free RAM just sitting there, it does nothing and I don`t know which smart ass even started comparing ROM optimization and free RAM.
Click to expand...
Click to collapse
Other than having less size for the battery(which is is untrue, you could just have one larger sized ram stick) having more ram does not lead to less battery life. Like i said before where did you hear that? Googling that only brings up the contrary so im confused where you got that information.
Sent from my SM-G900A using Tapatalk

Sending 15 photos via fb messenger causes crash because it needs more ram.
Free ram isn't FREE RAM, it's cached memory, it is still being used but if an needs more it will free it and the cached process will be moved to swap or forced close...and yeah have fun sending a support or bug report to facebook, because they're not fixing it.
Sent from my SM-G900F using XDA Free mobile app