Multitasking/RAM - OnePlus 2 Real Life Review

You're busy and don't have time to wait, which is why you need to stop reading this thread and get back to organizing your Pogs. Rate this thread to express how the OnePlus 2 performs when multitasking. A higher rating indicates that the OnePlus 2 keeps many apps in memory so that they don't need to reload, and that when moving between apps, transitions are smooth and performance is excellent.
Then, drop a comment if you have anything to add!

RAM
5 star; fast device.

Oxygen OS (2.2.0) uses ~1.5gb so there is about 2gb free for apps and what not. More than enough for daily multitasking.

The thing is, 1+2 never used all that ram, there is ALWAYS 1.5G free. why not cache more processes? the default ram settings must be aggressive.

More than 50% is consumed on installing just necessary files with games excluded!

With OSS 3.5.6, RAM utilization crossing 70%+ with minimal installed apps (No games).

Do you think we will get picture in picture soon on our phone
It.s such a nice feature !!

I have tested with 42 max app running in the background, still after that am able to play NOVA game with high details settings and absolute no lag, am using the official 3.5.8 OS.

Related

(Q) Droid Charge ram 328 or 512?

Sorry if this question has been answered somewhere, but I searched and couldn't find a reliable answer. When I go to task manager, it always shows memory usage out of 328mb available. Everything I read prior to purchase indicated there was 512mb ram. If I'm going to be locked in contract for any extended period of time I definitely need more than 328. 512 is already low by today's standard, but 328mb is ridiculously bad. Anyone that knows the answer and a way to verify would be greatly appreciated as all the searches I do come up with both answers.
Thanks for the help guys.
Sent from my SCH-I510 using Tapatalk
In addition to the above mentioned issue... I frequently have 250+ out of the available 328 used even when task manager indicates no apps running. Is there that much going on in the background? In case this helps I'm running the ED2 debloated rom so I can't imagine how bad it would be if I still had all the bloat in there.
Thanks again for the input
Sent from my SCH-I510 using Tapatalk
The phone has 512MB total, with some of that allocated to the system that can't be used by apps. This memory goes to thinks like the GPU to give you that stellar video performance. Sucks that it can't be changed really, but that is how it's setup. I believe that we can get a few MB back from the system, but you won't get all of it back.
imnuts said:
The phone has 512MB total, with some of that allocated to the system that can't be used by apps. This memory goes to thinks like the GPU to give you that stellar video performance. Sucks that it can't be changed really, but that is how it's setup. I believe that we can get a few MB back from the system, but you won't get all of it back.
Click to expand...
Click to collapse
Thanks a lot for the response. Makes me a lot more comfortable with holding on to this guy. There must be some serious bacground processes going. because I've yet to see anything lower than 180mb used (about 150 available) and that's with autokiller at extreme preset, which I normally wouldn't set so high...I just wanted to see if any additional mb's would free up.
Sent from my SCH-I510 using Tapatalk
Ok, android 101:
Android uses smart caching and background process management to keep your apps available and running smoothly. As such the more RAM you have free the more you are WASTING. This system is designed to run up to 99% RAM use before turning off any running apps/background processes.
Ever since android 2.2 it has been HIGHLY efficient at doing so. Using autokillers to keep RAM free is pointless, as most apps don't even use ANY CPU when in background, unless they perform background checks for things like is it your turn on words with friends, etc. Unless you have an app that uses too much background data like this (in which case I'd just get rid of the app...) then using killers is pointless, let the OS run the way it is designed to do. Ever since I listened to a ROM dev and stopped using task killers my battery life on my original droid has nearly tripled, and I'm overclocking it from 566 to 1200mhz!
Android is not windows 95, you don't need to hold its hand and make sure things are closed, doing so actually defeats the advanced features of the OS, decreases battery life in all but a very few cases, and increases your app startup times, keeps you from getting background updates properly, etc.
warriorprophet said:
Ok, android 101:
Android uses smart caching and background process management to keep your apps available and running smoothly. As such the more RAM you have free the more you are WASTING. This system is designed to run up to 99% RAM use before turning off any running apps/background processes.
Ever since android 2.2 it has been HIGHLY efficient at doing so. Using autokillers to keep RAM free is pointless, as most apps don't even use ANY CPU when in background, unless they perform background checks for things like is it your turn on words with friends, etc. Unless you have an app that uses too much background data like this (in which case I'd just get rid of the app...) then using killers is pointless, let the OS run the way it is designed to do. Ever since I listened to a ROM dev and stopped using task killers my battery life on my original droid has nearly tripled, and I'm overclocking it from 566 to 1200mhz!
Android is not windows 95, you don't need to hold its hand and make sure things are closed, doing so actually defeats the advanced features of the OS, decreases battery life in all but a very few cases, and increases your app startup times, keeps you from getting background updates properly, etc.
Click to expand...
Click to collapse
I was always of the impression that an app such as autokiller differed from a standard task killer in that it modified the values at which android natively kills off processes vs me going in and manually closing an app (which i never do). I too have read articles that task killers are pointless and do more harm than good, but I always thought autokiller was a different sort of "tweak" if you will. I've even seen several devs promote that they've modified androids native memory management to be more aggressive, etc...which is what I thought autokiller accomplished. Autokiller simply seemed necessary to me with the Charge because I was experiencing lag and lockups even with a debloated rom and voodoo kernel. Clearly there could be several culprits to this this and I was simply testing out different fixes and seeing what the results were. Thanks for the heads up though...learn something new every day.

Available RAM Dilemma on the Droid Charge

I'm currently running EP1F Debloated with Gummy Charged
The phone typically says that, out of 312MB of accessible RAM, there is 60MB or less of free RAM.
i'm running GO Launcher EX, and on it's RAM meter, it's almost always in the Red (signifying that it's almost Maxed out in available RAM)
is this normal?
of course, any time i quit all open applications, the usuals always reload, but then sometimes odd programs will run in the background (i.e., netflix, google+, music, amazon appstore, picasa, ustream, etc). These are programs that I haven't even loaded or ran. they just like to load themselves up and run in the background. so because of this, my available Free RAM tends to sit at 39-55MB. that seems VERY low to me. and may be the reason why my phone tneds to bog down a bit and lag every now and then, when i'm going from app to app.
I know EP1F doesn't have voodoo lagfix yet (like it did on EE4), but this unusually high consumption of RAM seems odd to me.
does anyone have any input on this?
appreciate it
If you havent ran, and don't run those programs just get rid of them
no no no... I definitely run them. but it's probably a few times a day, sporadically.
but i don't need them to be running in the background, hogging RAM. whereas, i'm totally fine with an app like Gmail to always be running, since i check that all the time.
I use Autokiller Memory Optimizer, set to "optimal" preset. It's not a task killer, it just changes Androids settings to close programs at different trigger points. Keep some free ram and keeps the system from bogging down.
I also use Autostarts, which disables programs from starting up at startup or for other notifications that are set. Some programs still start themselves but it helps.
Why do you want free RAM? Unused RAM is doing nothing for you, Used is holding a program ready to launch so it's faster and needs less CPU to launch. Ideal RAM usage is 100% because the system will automatically make room for a new program to run.
Have you ever gotten a message that an app can't launch due to low RAM? Using RAM doesn't mean using CPU or battery. It just means ready to run faster.
Sent from my (currently) stock Verizon Fascinate ed04 using XDA App.

Is the memory usage always so high?

Hey guys i have been enjoying my rooted sensation with ARHD 6.6.4 rom and its working perfect but i only have one issue.
Is the memory usage always so high?
I used this app called Memory Booster Lite and it shows used memory 75% and free only 23 or 25% always no matter how many apps or services i close.
Is this normal and is there any way to improve free ram memory?.
Thanks
Anything above 150 MB free memory is considered good in my books.
Most custom ROMs will get you between 200-250 MB free memory, which is normal.
You don't need to improve the amount of Free RAM you have at any given time. And your memory booster app is probably counter productive to achiving improved performance.
When you load an Android App, it will stay in RAM until something else needs that memory. It's not supposed to get dumped out of RAM just because you close the app.
If you have 100mb of RAM (using easy to work with numbers here) and an app takes 50 MB of RAM and anothe rapp takes 25MB of RAM, both apps will stay loaded in RAM so make them load quicker if you go to use them again. This saves load time and battery as the phone doesn't have to spend energy to transfer the app from storage back into RAM.
So in this scenario you'll have 25MB of RAM left.
Now say you want to load a 3rd app that takes 50MB of RAM. Obviously you don't have enough RAM to load it, so the system will now dump the other 50MB RAM user so it has room to load the new 50MB into RAM.
The system does it all for you natively so you don't need memory improvement apps. All they do it use up RAM permently (since they keep themselves in active memory and won't let themselves be killed) and use up extra battery power because they perform a task that will be performed again by the system later.
Android is very efficient at dumping apps form RAM when not in active use.
Over the course of a battery cycle you'll find that you use the same apps multiple times in a row. The phone app, text app, web browser app, etc are all things that you will use over and over and over. So rather than dumping these out of memory it keeps them so they load faster the next time. And it works VERY well. And it custom tailors itself to the user. If you never use the text app, but use Angry Birds all the time, Angry Birds will stick in RAM.
Sense is a RAM hog. If you want more RAM use AOSP. Having said that, free RAM is wasted RAM.
Sent from my HTC Desire S using xda premium
Skipjacks said:
You don't need to improve the amount of Free RAM you have at any given time. And your memory booster app is probably counter productive to achiving improved performance.
When you load an Android App, it will stay in RAM until something else needs that memory. It's not supposed to get dumped out of RAM just because you close the app.
If you have 100mb of RAM (using easy to work with numbers here) and an app takes 50 MB of RAM and anothe rapp takes 25MB of RAM, both apps will stay loaded in RAM so make them load quicker if you go to use them again. This saves load time and battery as the phone doesn't have to spend energy to transfer the app from storage back into RAM.
So in this scenario you'll have 25MB of RAM left.
Now say you want to load a 3rd app that takes 50MB of RAM. Obviously you don't have enough RAM to load it, so the system will now dump the other 50MB RAM user so it has room to load the new 50MB into RAM.
The system does it all for you natively so you don't need memory improvement apps. All they do it use up RAM permently (since they keep themselves in active memory and won't let themselves be killed) and use up extra battery power because they perform a task that will be performed again by the system later.
Android is very efficient at dumping apps form RAM when not in active use.
Over the course of a battery cycle you'll find that you use the same apps multiple times in a row. The phone app, text app, web browser app, etc are all things that you will use over and over and over. So rather than dumping these out of memory it keeps them so they load faster the next time. And it works VERY well. And it custom tailors itself to the user. If you never use the text app, but use Angry Birds all the time, Angry Birds will stick in RAM.
Click to expand...
Click to collapse
All of this. Every bit of it. I had to explain this to someone the other day who was hellbent on achieving MAXIMUM FREE RAM.
Skipjacks said:
You don't need to improve the amount of Free RAM you have at any given time. And your memory booster app is probably counter productive to achiving improved performance.
When you load an Android App, it will stay in RAM until something else needs that memory. It's not supposed to get dumped out of RAM just because you close the app.
If you have 100mb of RAM (using easy to work with numbers here) and an app takes 50 MB of RAM and anothe rapp takes 25MB of RAM, both apps will stay loaded in RAM so make them load quicker if you go to use them again. This saves load time and battery as the phone doesn't have to spend energy to transfer the app from storage back into RAM.
So in this scenario you'll have 25MB of RAM left.
Now say you want to load a 3rd app that takes 50MB of RAM. Obviously you don't have enough RAM to load it, so the system will now dump the other 50MB RAM user so it has room to load the new 50MB into RAM.
The system does it all for you natively so you don't need memory improvement apps. All they do it use up RAM permently (since they keep themselves in active memory and won't let themselves be killed) and use up extra battery power because they perform a task that will be performed again by the system later.
Android is very efficient at dumping apps form RAM when not in active use.
Over the course of a battery cycle you'll find that you use the same apps multiple times in a row. The phone app, text app, web browser app, etc are all things that you will use over and over and over. So rather than dumping these out of memory it keeps them so they load faster the next time. And it works VERY well. And it custom tailors itself to the user. If you never use the text app, but use Angry Birds all the time, Angry Birds will stick in RAM.
Click to expand...
Click to collapse
Wow thanks a lot for the explanation i really didnt know that.I got used to the pc ram optimizing hahahaha my bad.
so these apps android booster and memory booster shall i remove them all?
but apps running in background they dont drain ur battery?.
Like i am running music player and later i stopped it but its still there in process does it drain battery as long as its there in services?
High Always
Memory free has always been low to about 215 MB max. If you really want you can freeze sense and use a basic launcher from the play store to increase memory by about 50-70 MB.
Memory free is about 300 MB with Virtuous Inquesition 4.0.2 for me!
gamer1291 said:
Wow thanks a lot for the explanation i really didnt know that.I got used to the pc ram optimizing hahahaha my bad.
so these apps android booster and memory booster shall i remove them all?
but apps running in background they dont drain ur battery?.
Like i am running music player and later i stopped it but its still there in process does it drain battery as long as its there in services?
Click to expand...
Click to collapse
Yeah get rid of all that stuff.
And no, having an app loaded in RAM doesn't mean it's using processor power, which is what uses the battery. (Nor does it mean it's forcing the screen to stay on, which is your biggest battery drain)
Think of an app you just closed as a guy on a bus. He's just sitting there taking up a seat on the bus not bothering anyone. He doesn't weigh much compared to the bus itself so he's not decreasing the fuel efficiency of the bus. And when a little old lady needs to get on and have a seat, he'll gladly give up his seat for her and get off the bus....then patiently wait on the sidewalk for the next bus.
But as long as he's sitting on the bus quietly he's primed and ready to jump into the drivers seat if you need him to do so. Once he gets off the bus, it takes a second for him to reboard so he can drive.
well, all of this is so wrong... (this maybe true if gingerbread, but not ICS)
Read here:
http://developer.sonymobile.com/wp/2012/03/30/learn-about-the-technical-differences-between-gingerbread-and-ics/
http://source.android.com/compatibility/4.0/android-4.0-cdd.pdf
ICS is designed for 1GB RAM devices (eg: Galaxy Nexus),
and ICS need at least 340MB for linux user space + hardware functions (eg: camera, modem) + 64-128mb max for each running application
so ICS will need more ram than GB. that's why I think 100-150mb free ram isn't enough on Sensation-ICS, especially if you run heavy games that consume very big memory
Rotundjere said:
well, all of this is so wrong... (this maybe true if gingerbread, but not ICS)
Read here:
http://developer.sonymobile.com/wp/...ical-differences-between-gingerbread-and-ics/
http://source.android.com/compatibility/4.0/android-4.0-cdd.pdf
ICS is designed for 1GB RAM devices (eg: Galaxy Nexus),
and ICS need at least 340MB for linux user space + hardware functions (eg: camera, modem) + 64-128mb max for each running application
so ICS will need more ram than GB. that's why I think 100-150mb free ram isn't enough on Sensation-ICS, especially if you run heavy games that consume very big memory
Click to expand...
Click to collapse
Maybe you forgot nexus s or some phone with 512MB, i use it on ics and still smooth and no problem with gaming.
Google never explain how much ram requirements to run ics they just said about STORAGE minimum is 1GB.
One of the improvement of ics is on memory management, we can call it ram management.
In eclair you have to use ram management apps to kill your background tasks in order to run heavy apps smoothly, but in gb google made some improvement on ram management so we dont need an app anymore.
In ics google improve memory management again, thats why even you playing heavy games then minimize it and open browser or something else, you dont feel laggy browsing or because system will kill the game, and you have to start from scratch if you open the game again.
And 768MB is enough for me to run shadow gun, x-plane, gta 3.
Do some research before you say something mate.
And for free ram, i can get 300MB on MIUI sense based, but i dont even care, just leave it let system do the job.
C'mon, we dont need 300MB (except for show off ) what we need is smoothness and battery efficient.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
I thought that they did have rom management in older android versions. If all recent apps stayed open then it would crash the phone because it couldnt handle the load. And apps have different API levels which decided what apps were killed, depending on the kind of app(which you could change with an app). Ics and jb just have a better from management system. Correct me if I'm wrong
And could I hear more about the extra RAM?
Sent from my HTC Sensation 4G using xda premium
CerealFTW said:
I thought that they did have rom management in older android versions. If all recent apps stayed open then it would crash the phone because it couldnt handle the load. And apps have different API levels which decided what apps were killed, depending on the kind of app(which you could change with an app). Ics and jb just have a better from management system. Correct me if I'm wrong
And could I hear more about the extra RAM?
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thats what i mean, in eclair phone become laggy when opened a lot of apps, but fixed on GB and more optimized on ICS.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
haha my bad. And is there really a 300mb ram hack in miui? This is the first I've heard of it
Sent from my HTC Sensation 4G using xda premium
In linux, the expression goes "free RAM is wasted RAM."
chrisund123 said:
In linux, the expression goes "free RAM is wasted RAM."
Click to expand...
Click to collapse
not true anymore, modern linux distro such as Fedora16 64-bit (kernel 3.x) only consume 320 MB of 8GB total RAM and 0 MB swap after start-up (no prefetch by default)
---------- Post added at 12:57 AM ---------- Previous post was at 12:51 AM ----------
aimcr7 said:
Maybe you forgot nexus s or some phone with 512MB, i use it on ics and still smooth and no problem with gaming.
Google never explain how much ram requirements to run ics they just said about STORAGE minimum is 1GB.
One of the improvement of ics is on memory management, we can call it ram management.
In eclair you have to use ram management apps to kill your background tasks in order to run heavy apps smoothly, but in gb google made some improvement on ram management so we dont need an app anymore.
In ics google improve memory management again, thats why even you playing heavy games then minimize it and open browser or something else, you dont feel laggy browsing or because system will kill the game, and you have to start from scratch if you open the game again.
And 768MB is enough for me to run shadow gun, x-plane, gta 3.
Do some research before you say something mate.
And for free ram, i can get 300MB on MIUI sense based, but i dont even care, just leave it let system do the job.
C'mon, we dont need 300MB (except for show off ) what we need is smoothness and battery efficient.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
yes of course you can run on sensation, but the system must kill other app running on background (just like my old moto milestone with 256mb ram kill app very frequently including homescreen launcher and it's very slow to start an app).
Read again the official Android 4.0 Compatibility Definition document:
http://source.android.com/compatibility/4.0/android-4.0-cdd.pdf
http://developer.sonymobile.com/wp/...ical-differences-between-gingerbread-and-ics/
Do some research before you say something mate.
sure, nexus s meet the android 4.0 ccd because it has more than 340 MB RAM, but it struggle just like 512 MB sony devices
128MB is a MUST for each app, but have to adjust more if needed. So next year or two, all phone manufactures will not ship devices with 512MB anymore coz it's too slow & will kill app on background frequently (just like my old milestone)
if you're not developer you won't encounter about memory hungry app, currently I make 3D games on android and <512MB devices (such as xperia mini ics) will automatically exit, because my game take to much ram and probably draw calls (but run very well on my pc), optimization is the only solution (reducing vertices/poly & texture size)
gamer1291 said:
Hey guys i have been enjoying my rooted sensation with ARHD 6.6.4 rom and its working perfect but i only have one issue.
Is the memory usage always so high?
I used this app called Memory Booster Lite and it shows used memory 75% and free only 23 or 25% always no matter how many apps or services i close.
Is this normal and is there any way to improve free ram memory?.
Thanks
Click to expand...
Click to collapse
haha.. you want more free memory? stop using a SenseUI rom...
trust me, youll get used to it. sense is nothing special after you get the full affect of an AOSP base
ALSO, just because memory is not free doesnt mean the memory isnt being allocated correctly. androids memory management is very intelligent. usually you dont need any task killers
chrisund123 said:
In linux, the expression goes "free RAM is wasted RAM."
Click to expand...
Click to collapse
Up to a point but beyond a certain threshold too little ram can cause lag, look in the v6 supercharger thread for more info on this
CerealFTW said:
haha my bad. And is there really a 300mb ram hack in miui? This is the first I've heard of it
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
You can easily reach 280MB free on MIUI sometimes 300MB. But c'mon, do you really need it?
Rotundjere said:
not true anymore, modern linux distro such as Fedora16 64-bit (kernel 3.x) only consume 320 MB of 8GB total RAM and 0 MB swap after start-up (no prefetch by default)
---------- Post added at 12:57 AM ---------- Previous post was at 12:51 AM ----------
yes of course you can run on sensation, but the system must kill other app running on background (just like my old moto milestone with 256mb ram kill app very frequently including homescreen launcher and it's very slow to start an app).
Read again the official Android 4.0 Compatibility Definition document:
http://source.android.com/compatibility/4.0/android-4.0-cdd.pdf
http://developer.sonymobile.com/wp/...ical-differences-between-gingerbread-and-ics/
Do some research before you say something mate.
sure, nexus s meet the android 4.0 ccd because it has more than 340 MB RAM, but it struggle just like 512 MB sony devices
128MB is a MUST for each app, but have to adjust more if needed. So next year or two, all phone manufactures will not ship devices with 512MB anymore coz it's too slow & will kill app on background frequently (just like my old milestone)
if you're not developer you won't encounter about memory hungry app, currently I make 3D games on android and <512MB devices (such as xperia mini ics) will automatically exit, because my game take to much ram and probably draw calls (but run very well on my pc), optimization is the only solution (reducing vertices/poly & texture size)
Click to expand...
Click to collapse
Maybe 2 years later google will optimize more this beautiful os so it wont become recource hungry OS, do we really need smartphone with 4gb ram? So it will become so smooth.
Ive tried samsung GS advance and its smooth, maybe samsung do better job in term of software. but oh, i forgot GS advance still on GB
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
And i do some research before wrote all this, i used to developed some rom for Neo.
And c'mon what SE said about ICS is ****, even their GB is laggy, too much issue, and when ics come, some people including me trying to make it smoother. But still there is an annoying issue with video recording.
Ive readed the link.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2

[Q] RAM ISSUES with samsung galaxy tab 2 7.0 (GT-P3100)

I own a samsung galaxy tab 2(GT p3100), which initially had 4.0.4 ICS with 687 MB RAM(but specified as 1 GB RAM, as some developers claim that it is being reserved for system). I updated my firmware to 4.1.2 and now it showed me 770 MB RAM. later i rooted my device and installed the latest CM(cyanogenmod) 10.1 (jelly bean 4.2). To my surprise this rom which has less bloatware and is smoother, it showed me 691 MB RAM, less than 770 MB as displayed by the STOCK jelly bean OS.
i would like to ask, which OS(custom/stock) displays the MAX RAM for GALAXY TAB 2 7.0(P3100)???????
as i don't ve enough internet downloading capacity(limited downloads), i can't just go on downloading all the firmwares and keep flashing everytime, SO EXPERIENCED USERS, PLEASE SUGGEST.
for more info(for my knowledge), do please tell this also--------->tab 2(my device specifies 1 GB RAM and the same does galaxy s2, but why with ICS(4.0.4) installed both the devices show different MB RAM. tab2 shows around 680 MB wheras S2 shows around 880 MB, wheras HTC one X shows 1 GB.
why is this so????? i know some developers claim that this RAM is being consumed by system or reserved for system, but why is it different for different devices, when the OS is the same?????
again if you claim that it is reserved by the android system, then WHY DO , WITH NO APPS INSTALLED TOO, I SEE AROUND 300-400 MB RAM BEING USED(300 MB WHEN I DNT USE ANY WIDGETS AND ALL, AND I STOP ALL THE PROCESSES, BY CLICKING FORCE STOP ON ALL APPS LIKE GMAIL AND EVERYTHING EXCEPT ANDROID SYSTEM AND PHONE AND SOME NECESSARY RED MARKED APPS IN THE DEFAULT TASK MANAGER).
if android process is being displayed here with this 770 MB ram, then where has the 230 MB ram gone------------>do you mean the android process consumes the hidden RAM and also a part of this RAM too???????------------------>this sounds too unpleasant, when htc one x displays all the specified RAM but my tab fails.
really disapponting
You are getting too excited about available RAM. The OS system manages available RAM so each different ROM will use it a little more or less.
The amount of free RAM has nothing to do with how many apps are stored, ONly how many apps are RUNNING. Android system efficiently manages RAM and tries to keep it about 80% full all the time. So called Bloatware (one mans bloat is another mans useful app) has nothing to do with speed , they do nothing if you don't run them.
The system RAM usage contained OS buffers, temp storage and system routines that are always loaded for speed.
1GB is a ton of RAM for android.
You do not have a RAM issue.
You can run out of SD storage space for downloaded apps if you store too many. But you have several GBs of storage so that's hard unless you are a real pack rat.
DigitalMD said:
You are getting too excited about available RAM. The OS system manages available RAM so each different ROM will use it a little more or less.
The amount of free RAM has nothing to do with how many apps are stored, ONly how many apps are RUNNING. Android system efficiently manages RAM and tries to keep it about 80% full all the time. So called Bloatware (one mans bloat is another mans useful app) has nothing to do with speed , they do nothing if you don't run them.
The system RAM usage contained OS buffers, temp storage and system routines that are always loaded for speed.
1GB is a ton of RAM for android.
You do not have a RAM issue.
You can run out of SD storage space for downloaded apps if you store too many. But you have several GBs of storage so that's hard unless you are a real pack rat.
Click to expand...
Click to collapse
Right Sir,
well, regarding storage i dont ve any issue as some data like pics and vids can be kept in ext storage card too,but i also wanted to know which ROM provides user with more RAM, so that it will be good for multitasking or if i play high end games like NFS MW
fbh59 said:
Right Sir,
well, regarding storage i dont ve any issue as some data like pics and vids can be kept in ext storage card too,but i also wanted to know which ROM provides user with more RAM, so that it will be good for multitasking or if i play high end games like NFS MW
Click to expand...
Click to collapse
The amount of difference between one kernel and another (which is what really matters here) isn't large enough to make any real difference in the performance of any application. The available RAM after the kernel grabs its stuff varies around 10% from one kernel to the next.
If you want to make a performance impact, make sure you minimize the number of running applications that compete for the available RAM. However, that won't make much difference as Android is very aggressive about grabbing memory back from idle applications.
Basically, you're obsessing over something that in the end will make no difference in how your tablet runs.
fbh59 said:
Right Sir,
well, regarding storage i dont ve any issue as some data like pics and vids can be kept in ext storage card too,but i also wanted to know which ROM provides user with more RAM, so that it will be good for multitasking or if i play high end games like NFS MW
Click to expand...
Click to collapse
Irrelevant. Android will clear apps from RAM if it's needed by an app with high memory usage. This isn't windows
Sent from my DROID3 using xda premium
well, if this is the thing, and android can kill apps automatically then why do some people prefer custom ROMs like CM or AOKP.
even for installing custom ROMs they need to root their tab/phone, and if they root and want to get rid of so called bloatwares and make their OS lightweight, they can uninstall it using root uninstaller(available for free in google play)....
but why do they prefer custom ROMS?????
fbh59 said:
well, if this is the thing, and android can kill apps automatically then why do some people prefer custom ROMs like CM or AOKP.
even for installing custom ROMs they need to root their tab/phone, and if they root and want to get rid of so called bloatwares and make their OS lightweight, they can uninstall it using root uninstaller(available for free in google play)....
but why do they prefer custom ROMS?????
Click to expand...
Click to collapse
More features generally. Some roms will manage the memory better than others, ie at what point it starts to kill apps to free RAM(although this can be adjusted in any rom using rom toolbox or a similar app). many custom roms include a theme engine allowing more customiza. They may make better use of resources to decrease battery usage or because it has better cpu governors which will increase performance. They may flash a custom roms because it's kernel includes modules that aren't in the stock Kernel. There are many reasons besides RAM usage, since as you say you can root and remove bloatware and change memory handling(called minfree or oomut of memory)
Sent from my DROID3 using xda premium

[MOD] Fixing N7's RAM issues

The following are two ram optimising scripts that actually do something. They will ensure a fluid experience by keeping a minimum of 100mb of ram free. Simple as that.
STEPS:
Download zip and extract files "boost" and "freeram".
On the tablet , use a root file manager
Paste files in /system/bin (system needs to be re-writable obviously)
Set permissions to rwxr--r--
Activate scripts manually after every boot using android terminal emulator:
1) free ram (to see ram usage)
2) su
3) freeram (no spaces)
4) boost
5) free ram (to see ram usage - compare to values in step1)
6) Profit
Explanation:
"boost" - activates Adrenaline Boost V3 (i take no credit for this script). What this does is clear the ram cache, freeing up ram storage.
"freeram" - a script i made, adjusts minfree values (android's built in ram manager) to kill off more empty apps from ram when ram usage exceeds certain values - not a task killer, so doesn't affect battery life
In android terminal emulator:
"su"
"cat /sys/module/lowmemorykiller/parameters/minfree"
-will show you the prior minfree values, "freeram" script adjusts these to 8192, 10240, 12288, 21000, 23000, 26000
Notes:
All changes reset on boot, so you'll need to to run everytime you reboot
check your ram usage before with: "free ram"
These two scripts will generally ensure about 300-400mb free ram always.
Removing widgets will improve this also.
If after a while nexus is feeling slow again, run "boost" script.
Fstrim or "lagfix" also helps with those having slow emmc issues
Enjoy more free ram
Or download an app called autokiller memory. Works miracles
mrazndead said:
Or download an app called autokiller memory. Works miracles
Click to expand...
Click to collapse
didn't know about that app.
This is more geeky and cleaner though, who doesn't want to use terminal??
And i don't think the app flushes the ram cache (similar to the adrenaline v3 script)
According to anandtech:
"I’m told that TRIM support has been part of the eMMC standard since around version 4.2, it was just a matter of enabling it in software. The result is that the new Nexus 7 shouldn’t have these aging affects at all. Better yet, fstrim support has also been added to the old Nexus 7 with as of the Android 4.3 update, so if you’ve got a Nexus 7 that feels slow, I/O performance should get better after fstrim runs in the background. I'm checking on whether the other Nexus devices have also had TRIM support added. I would consider the slow storage aging problem fixed as of now, and Google took the eMMC and storage I/O performance issues with the previous Nexus 7 to heart for this version."
Link: http://anandtech.com/show/7176/nexus-7-2013-mini-review/4
So that's good news for poorly ageing nexus 7's, just update to 4.3 instead of running lagfix
@mods: close/move the thread please.
this is another minfree / lowmemkiller script like Supercharger V6 which offers nothing more than actually less memory. What do I mean? It makes the device start killing apps/processes much sooner rendering it multitask-less. Provides a boost but at a terrible cost: much less mem available to apps...
I was able to multitask smoothly between 8 open apps without reloads. And I've been using this setup for 2mths or so.
I had memory issues with my n7, and this solved them, and I wanted to share as users (can't remember the thread name) were discussing slowness due to limited free ram, and this worked for me.
Mods feel free to close, sharing experiences is not appreciated obviously..
mpokwsths said:
@mods: close/move the thread please.
this is another minfree / lowmemkiller script like Supercharger V6 which offers nothing more than actually less memory. What do I mean? It makes the device start killing apps/processes much sooner rendering it multitask-less. Provides a boost but at a terrible cost: much less mem available to apps...
Click to expand...
Click to collapse
So basically, the Xda crowd is too dumb to make up their own minds?
Shouldn't it be up to the individual to try this (and any other) mod freely. Your personal experience with similar mods is welcome, but you trying to tell others what is best for them is way out of line imo.
IceColdJellied One X
Tapatalk 4 Beta
Shared knowledge = more knowledge imho
Thanks for sharing it! :beer:
On linux systems having a little amount of free ram is not necessarily a bad thing. it means that the apps you use most are available to be opened very quickly.
OP: what do you mean by "empty app"?
Appreciate your effort, OP. However, a more user-friendly way is to install an app like Rom Toolbox(and others) and change minfree. RT has presets, and set at boot features. I personally subscribe to the thought process that unused ram is wasted ram.
Nbsss said:
According to anandtech:
"I’m told that TRIM support has been part of the eMMC standard since around version 4.2, it was just a matter of enabling it in software. The result is that the new Nexus 7 shouldn’t have these aging affects at all. Better yet, fstrim support has also been added to the old Nexus 7 with as of the Android 4.3 update, so if you’ve got a Nexus 7 that feels slow, I/O performance should get better after fstrim runs in the background. I'm checking on whether the other Nexus devices have also had TRIM support added. I would consider the slow storage aging problem fixed as of now, and Google took the eMMC and storage I/O performance issues with the previous Nexus 7 to heart for this version."
Link: http://anandtech.com/show/7176/nexus-7-2013-mini-review/4
So that's good news for poorly ageing nexus 7's, just update to 4.3 instead of running lagfix
Click to expand...
Click to collapse
I wish My poorly aging Nexus 7 hasn't improved at all since the 4.3 update. In fact I think it's running even slower. I haven't run lagfix since the update though since I lost root and I'm waiting for Wug's updated toolkit to get it back. (I know I can restore root with other methods but I'm lazy and toolkits just make it easier.)
Aside from the TRIM issue I loved my old Nexus, but 16gb just wasn't enough space anymore and any time I dipped below 4gb of remaining storage it would lag so horribly I'd have to wipe the whole thing and start over if I wanted it to be buttery smooth again, even after using lagfix. Lagfix helped a bit, but it was still crawling compared to a freshly wiped tablet.
I've got a 2013 Nexus 7 on the way though so hopefully what you said about TRIM on the newer model is true and this one won't age as poorly as the original. Even if it does, having an extra 16gb of wiggle room can't hurt.
My thoughts
The most aggressive lvl on the minfree script is 26K ie 26,000*4/1024 = 101mb
Having less than 100mb of ram (ie over 90% ram used) slows down my n7 and its really bad when i have 19-45mb of ram left...
The fact that the script resets on reboot means i can easily compare the difference, for ME it helps and i can't notice an impact on multitasking (and thx for teaching me how to use terminal to check ram usage )
mrazndead said:
Or download an app called autokiller memory. Works miracles
Click to expand...
Click to collapse
Since i use this app my ram is always ok. Thanks so much, really improved a lot

Categories

Resources