Related
Please I need some help
I want to know how to edit the EXROM and modify it and maybe remove it
Please in details and if I remove it am I going to gain more space in RAM
Another question why RAM in jam is 57 instead of 64 as they said in the commercial and in the web site
Bad English right
Hi.
First of all:
You won't get any more RAM by removing ExtROM.
It is possible to gain more "Storage" by changing amount of ExtROM. (Your device's persistent memory [ROM] is divided into "Storage" and ExtROM).
I'd recommend you, not to tamper with ExtROM too much.
The reason you see less than 64MB of RAM is simple. System uses small amount all the time. But that's not that much.
If you want your problems with memory to go away forever, just but a nice SD memory card.
Then, you should install all programs in "Storage Card", and you always have planty of RAM and ROM free.
As for 64MB of RAM... don't cry about that. If you'd have 128MB, your device would have nearly 2 times shorter battery standby time.
Notice that newer devices (especially WM2005 ones) come with 64MB RAM not 128. That's because they come with much more ROM, and try using ROM to store all data. That makes them save energy, which is neded to keep RAM alive.
Have fun.
Can anyone direct me to a guide somewhere?
I'd like to make an ext partition? Or would I? Is Swapper 2 just as fast? Tradoffs? Anyone run into their sd card wearing out yet?
bueler?
The message you have entered is too short. Please lengthen your message to at least 10 characters.
The consensus seem to be "do not use" except as 'last resort', and only needed on phones with 256MB or less of mem.
I wrote this, and I am waiting for a technical review from some experts in this field.
http://forum.xda-developers.com/showthread.php?t=897823
kschang said:
The consensus seem to be "do not use" except as 'last resort', and only needed on phones with 256MB or less of mem.
I wrote this, and I am waiting for a technical review from some experts in this field.
http://forum.xda-developers.com/showthread.php?t=897823
Click to expand...
Click to collapse
I have 256MB ram
At the moment, Compcache is good enough, but I can't help but wonder how much better it could be with swap instead of Compcache.
edit: "For example, If you have a 256MB system (shows as 262MB due to 1024 vs. 1000 KB size difference) and have 130MB of apps and data/cache loaded, then that leaves about 130MB for the system to actually RUN programs. That sounds like a lot, but in reality that is not enough, since the system itself takes 50-80MB, and services will take up another 30-50MB, leaving almost nothing. "
quick review, you don't appear to be differentiating between RAM and Flash? Having more apps installed shouldn't increase RAM usage at all. Unless I gravely misunderstand the Android OS, if I install a new program, it resides in the system flash, not the RAM, until I run it, at which point it gets loaded to RAM. When the system needs memory and no swap or Compcache is in use, it writes the state of the application to the flash and removes it from RAM.
What the swap does is similar to what compcache does-- compresses apps that are currently in RAM, and moves them to the swap space. In the case of Compcache, this is in the RAM. But since you're compressing it, background apps don't take nearly as much RAM, and you get an app switching speedboost because the processor can uncompress the compcache'd program, "move" it to RAM, compress the currently running program in RAM, and "move" it to the compcache. Forgive me if you already said this, I can't read the entire thing at the moment.
As for swap, I'm not sure if the processor compresses before going to the hard swap file, I don't think that it does-- when android starts getting low on RAM, it moves what was in RAM, to the swap on the SD-card. Since it does this when the system is low on RAM, and not when the system runs out of RAM, you never notice it. Reading the app back from the SD card happens almost instantaneously, because the sd cards can be read from at a speed of at least 20MB/s, maybe more. When you're restoring an app to RAM, 20MB/s is plenty.
edit2: I'm sorry but this guide is too vague to be anything more than moderately informative. Comments like:
-"CompCache, or "compressed cache", is handled by the Linux kernel. It takes a portion of your memory, and use it as a cache space, but compressed. By using on-the-fly compression it is able to make your memory appear to be a bit larger than it actually is. However, the result is slower performance.
This is usually NOT tweakble without mod ROM such as Cyanogen Mod. The kernel also must support this feature, and not all do. This also slows your phone. "
-"...swap space by either creating a swap file or a swap partition. This adds a lot of read/write action to your SD card and may substantially decrease its usable life."
-"This really slows your phone."
People wouldn't be doing these things for no reason. Compcache does not "make your memory appear a bit larger", when it at least doubles the amount of usable RAM-- when you allocate 60MB, if you average 75% compression (I usually see between 65% and 80%), do you know how much RAM this effectively nets you? Over at least 60MB extra, usually about 80! So my phone goes from having 256MB ram to having 340 effectively. Having your processor overclocked minimizes any slowdown from the compression/decompression; I haven't noticed any slowdown, and having the "extra" RAM definitely has made my phone more able to multitask.
You basically discourage users from doing ANYTHING like swapping, compcaching, etc to their phone, saying it "slows it down" and "can substantially decrease your SD Card's life". My experience has been otherwise regarding slowing it down, and regarding the SD card, the only part that would actually go bad is the swap partition. If you put that at the end of the drive, when it goes bad, you'll know, and you can just move the partition back 300MB and put your 300MB swap there. We haven't heard of any users' cards going bad from this yet. Also, if you have a class 6+ SD Card, they implement wear leveling on the card, so you don't need to worry about wearing out any individual bits.
Sorry, I'm just not digging it.
rancur3p1c said:
I have 256MB ram
Click to expand...
Click to collapse
Me too, me too...
At the moment, Compcache is good enough, but I can't help but wonder how much better it could be with swap instead of Compcache.
Click to expand...
Click to collapse
So try it. With CM612, I have CompCache AND Swap (through Swapper2 / 128 MB) turned on. It slows down every once in a while but my programs don't crash any more.
edit: "For example, If you have a 256MB system (shows as 262MB due to 1024 vs. 1000 KB size difference) and have 130MB of apps and data/cache loaded, then that leaves about 130MB for the system to actually RUN programs. That sounds like a lot, but in reality that is not enough, since the system itself takes 50-80MB, and services will take up another 30-50MB, leaving almost nothing. "
quick review, you don't appear to be differentiating between RAM and Flash? Having more apps installed shouldn't increase RAM usage at all. Unless I gravely misunderstand the Android OS, if I install a new program, it resides in the system flash, not the RAM, until I run it, at which point it gets loaded to RAM. When the system needs memory and no swap or Compcache is in use, it writes the state of the application to the flash and removes it from RAM.
Click to expand...
Click to collapse
At first I thought the same way you did, until I started looking in "diskusage".
According to diskusage, there is no separate RAM. 256MB is 256MB. App storage is where everything goes, and what's left is used to load services and such. The numbers I added up matches. I have 256 MB phone. 100 is for apps, which leaves about 150-160. System itself takes 50-80 (acore, gapps, phone, system...) then add a few services and you're down to 30-40 MB free to actually run the programs. The numbers seem to match up to what's shown at the bottom of "Manage Services".
I know it's weird, but perusal of Android developers kit doesn't contradict this understanding.
What the swap does is similar to what compcache does-- compresses apps that are currently in RAM, and moves them to the swap space. In the case of Compcache, this is in the RAM. But since you're compressing it, background apps don't take nearly as much RAM, and you get an app switching speedboost because the processor can uncompress the compcache'd program, "move" it to RAM, compress the currently running program in RAM, and "move" it to the compcache. Forgive me if you already said this, I can't read the entire thing at the moment.
As for swap, I'm not sure if the processor compresses before going to the hard swap file, I don't think that it does-- when android starts getting low on RAM, it moves what was in RAM, to the swap on the SD-card. Since it does this when the system is low on RAM, and not when the system runs out of RAM, you never notice it. Reading the app back from the SD card happens almost instantaneously, because the sd cards can be read from at a speed of at least 20MB/s, maybe more. When you're restoring an app to RAM, 20MB/s is plenty.
edit2: I'm sorry but this guide is too vague to be anything more than moderately informative. Comments like:
-"CompCache, or "compressed cache", is handled by the Linux kernel. It takes a portion of your memory, and use it as a cache space, but compressed. By using on-the-fly compression it is able to make your memory appear to be a bit larger than it actually is. However, the result is slower performance.
This is usually NOT tweakble without mod ROM such as Cyanogen Mod. The kernel also must support this feature, and not all do. This also slows your phone. "
-"...swap space by either creating a swap file or a swap partition. This adds a lot of read/write action to your SD card and may substantially decrease its usable life."
-"This really slows your phone."
People wouldn't be doing these things for no reason. Compcache does not "make your memory appear a bit larger", when it at least doubles the amount of usable RAM-- when you allocate 60MB, if you average 75% compression (I usually see between 65% and 80%), do you know how much RAM this effectively nets you? Over at least 60MB extra, usually about 80! So my phone goes from having 256MB ram to having 340 effectively. Having your processor overclocked minimizes any slowdown from the compression/decompression; I haven't noticed any slowdown, and having the "extra" RAM definitely has made my phone more able to multitask.
Click to expand...
Click to collapse
It also seriously depends on your SD card. I've read reports on Phandroid that said class 6 or 8 microSD cards would provide almost lag-free swaps, but that's on a G1 (which is already a slow phone).
You basically discourage users from doing ANYTHING like swapping, compcaching, etc to their phone, saying it "slows it down" and "can substantially decrease your SD Card's life". My experience has been otherwise regarding slowing it down, and regarding the SD card, the only part that would actually go bad is the swap partition. If you put that at the end of the drive, when it goes bad, you'll know, and you can just move the partition back 300MB and put your 300MB swap there. We haven't heard of any users' cards going bad from this yet. Also, if you have a class 6+ SD Card, they implement wear leveling on the card, so you don't need to worry about wearing out any individual bits.
Sorry, I'm just not digging it.
Click to expand...
Click to collapse
Constantly reading and writing the file will cause that area to get much heavier use and eventually cause it to fail the bootup "checking SD card". The only question is how much life is taken away.
I am running my Droid on 24% CompCache AND 128MB Swap right now. Occasional lag but otherwise runs quite well. It's also overclocked to 1.2 GHz with P3Droid's kernel. So I do practice somewhat of what I preach...
so if I have 512MB of ROM, and 256MB of RAM, and I fill up my ROM with programs, how much RAM do I have?
I don't follow how what you said can be.
SD Card writes-- SanDisk guarantees theirs for 100K writes to any given sector...that's good enough for the swap to not be a problem in the near future IMHO.
let's put it this way...
Here's the specs of Moto Droid from Motorola itself (http://developer.motorola.com/products/droid/)
RAM 256 MB
FLASH ROM 512 MB
USER STORAGE AVAILABLE (MAX) 256 MB
So the REST of the ROM clearly is to hold the Android OS itself. The actual programs you can load for running? 256MB. That's app storage.
I've always wondered if there's a way to read the actual ROM contents and enumerate that... But that's for another topic.
Found this useful post: boot process of Android OS
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
Furthermore, I noticed that the "built-in" apps (i.e. bloatware) are actually just stuff left in the "system" dir which can only be accessed with root permission. So they are NOT store in "ROM" per se, but more like "part of boot rom".
I have to find explanation on how an app is loaded, but that helps...
Aha, so that's the term they used... Application Lifecycle.
http://www.youtube.com/watch?v=ITfRuRkf2TM
Okay, I take back what I said. Apps are loaded into RAM, but HOW things are allocated wasn't that clear.
From what I understand, apps, when they are killed by system, some exit gracefully by writing their instance "state" (data and cache) to app storage. Some just exits.
Browser will write the URL, for example. When the browser is "resumed", the process is loaded, then the instance loads back the URL and it's as if nothing happened.
I'll have to revise the paper, AND I haven't figured out what to say about swap and compcache yet.
Made some corrections.
On 256MB machine, 30MB is used by deep system buffers (not part of OS), another 32 for OS cache, so about 190 or so is available the OS itself to load apps and services, and just the default gapps, system, phone, and so on is about 60MB. So a fresh clean phone should ahve no more than 120-130 MB free. If you load a couple apps with autostart services, it'll quickly drop below 50MB.
http://stackoverflow.com/questions/2298208/how-to-discover-memory-usage-of-my-application-in-android
Another piece of the puzzle... The numbers at the bottom of "Manage Services" is as explained below:
(quoting from http://android-developers.blogspot.com/2010/02/service-api-changes-starting-with.html )
"Finally, along the bottom of the screen are some obscure numbers. If you know how to interpret them, this gives you a lot of information on the memory status of your device:
* Avail: 38MB+114MB in 25 says that the device has 38MB of completely free (or likely used for unrequired caches) memory, and has another 114MB of available memory in 25 background processes it can kill at any time.
* Other: 32MB in 3 says that the device has 32MB of unavailable memory in 3 unkillable processes (that is, processes that are currently considered to be foreground and must be kept running)"
The order is reversed in Android OS 2.2. Mine says
Other: 75MB in 5 Avail: 18MB + 20 MB in 3
Which should mean 75MB in 5 unterminable tasks, 18 MB free (or can be freed easily), plus another 20 MB used by 3 processes that can be killed to free up.
ProCrank says...
39911K System_server
15756K acore
12982K swiftkey
10136K DIY Screensaver (lock screen)
9392K Phone (system)
9093K ATKfroyo
6834K Terminal
3984K JuiceDefender
3785K Screebl
3482K system MMS
3329 SeePU
3244K Bluetooth
3199K SetCPU
1979K Zygote (which is Dalvik init)
1425K Mediaserver
and the rest is native system code well under 1MB in size.
If you add System_server, Phone, Zygote, Acore, and foreground app (terminal and procrank) you get about 75MB. It would be nice if that screen TELLS you which program it considers to be unterminable, but, oh well...
Does the 768 RAM on the MyTouch 4G allow installing more apps or is the memory reserved for apps/data the same as for a 512 device?
Thanks.
I think you are confusing the memory used for storage (1gb available internally) with the memory used for running apps (768mb).
You have 768mb of system memory (for running apps). 1gb of internal memory for apps/storage along with 8gb on the removable SD card.
What are you talking about man?
RAM = random access memory.
ROM = Read only memory.
Ram is what used to allocate the programs/app that is already installed on ROM, so it can run on the phone. In simple ROM is where you install it and to run the program when you load it then its allocated in RAM, I hope it make sense to you.
I've currently got an Acer Liquid E which has 512 MB RAM but I need an AWS phone now.
The phone has 512 MB RAM but only part of that is allocated for storing apps and their data. I believe after a clean wipe only around 70 MB is available for apps (I could be wrong about that number). I believe the rest of the RAM is reserved for the OS and various caches. Even though many apps can be moved to the SD card, there always remains part of the app taking up memory in RAM so if you install too many apps you'll eventually run out of space and things get ugly.
So my question is whether the larger amount of RAM (an extra 256MB) is (at least partially) available for a larger amount of app space, or whether the amount of space available for apps is the same as on a 512MB device, with the additional 256MB being used only by the OS...
I'm sure I've got some of the details wrong, but still the basic question: can the MyTouch 4G have more apps installed before going wonky than say a Samsung Vibrant?
Thanks!
No wonder you got confused I just looked up the spec for Acer Liquid E. It has 512MB ram and rom. Now you are saying that you installed alot of apps and its becoming sluggish? In that case disable some of the service and close some apps you don't use. Normally you won't have 512MB or the actual ram in any device as OS itself and other things use some memory some even used for accelerated graphic depending on the phone.
What you should look for is first remove all the boltware and run the phone barebone without running many things then you can see how much actual memory is available to you to run other service/apps. Also you can save the app as in installing in SD but that has nothing to do with the RAM which is just saving in SD and not in NAND. But when you run the app it will still have to be allocated on RAM thus enabling you to use it.
On my system the RAM appears to be partitioned into /system, /data, and /cache. It seems the /data partition is what's available for use by apps. When this gets low (around 20 MB or so) performance is seriously affected and some apps don't even work right. On my system there is 200MB available for data. I assume it's similar on other devices with 512 MB RAM.
One way to check is install the free app "App 2 SD Free" and on the "On phone" tab at the bottom it will give you total and available memory. (I'm sure there are lots of other ways to check, but it's one app I've got installed that has this info. Here's a link: whoop's it won't let me post a link...)
Anyway, what I'm trying to find out is if there's more available memory on the MyTouch 4G. If someone with this phone could run this app let me know what the "total" memory "On Phone" is I'd appreciate it!
Thanks!
tmagritte said:
On my system the RAM appears to be partitioned into /system, /data, and /cache. It seems the /data partition is what's available for use by apps. When this gets low (around 20 MB or so) performance is seriously affected and some apps don't even work right. On my system there is 200MB available for data. I assume it's similar on other devices with 512 MB RAM.
One way to check is install the free app "App 2 SD Free" and on the "On phone" tab at the bottom it will give you total and available memory. (I'm sure there are lots of other ways to check, but it's one app I've got installed that has this info. Here's a link: whoop's it won't let me post a link...)
Anyway, what I'm trying to find out is if there's more available memory on the MyTouch 4G. If someone with this phone could run this app let me know what the "total" memory "On Phone" is I'd appreciate it!
Thanks!
Click to expand...
Click to collapse
You have your definitions messed up:
You are talking about ROM (read only memory) which is like hard drive in your computer. MT4G has 2gb of memory with about 1gb available to end user. SD card can be used to supplement ROM, if app developers enable it (most do) so you have the potential to have up to 17gb of storage space for apps.
RAM (random access memory) is what used to actually run those apps (i.e ability to multitask) and so far this phone has more RAM then any other phone on the market (768MB).
In short: you have roughly 5 times more available memory for apps then on old phone and that does not even include SD card.
Does that help?
Ignore this post: read the one below.
OK, I think I've been confused because the Acer has 512 MB RAM and ROM. So as I understand it now, there's some amount of ROM on the phone that is available to install apps and separate from this is the RAM used to run the apps. I'm guessing the amount of RAM taken up by apps depends on the apps and services currently running, not on the total installed in the ROM?
So having more ROM will let you install more apps but having more RAM will be better for multitasking and speed since more apps can reside in RAM before being swapped out?
From what I've picked up on this thread and Google:
MyTouch 4G: 758 MB RAM, 1 GB user ROM
Vibrant: 512 MB RAM, 2 GB user ROM
Liquid E: 512 MB RAM, 200 MB user ROM
The Vibrant can have more apps installed but the MyTouch should be better at multitasking (and 1 GB space for apps seems like plenty). Either phone should be far better than the Liquid which is seriously constrained by the small ROM.
Is this generally correct? If so, I'm definitely leaning towards the MyTouch 4G.
thanks!
Yes thats some what correct. In this case you might want to go with MT4G due to superior hardware capabilities. Vibrant has issues and you will need lagfix before you can work it fully but on MT4G is good to go out of the box if you are android normal user.
If you look at quadrant benchmarks for Vibrant against MT4G. The MSM8255 (2nd gen snapdragon) CPU and Adreno 205 GPU blows away the Hummingbird CPU and SGX 540 GPU. ATM MT4G and DHD is the fastest android device in market. With MT4G you have elegant balance in ROM/RAM for nice performance. BTW MT4G has 4GB ROM but 1GB user accessible.
Thanks. I'm going to try and get the MT4G.
Hello,
I'm trying to fill a table useful to understand how much RAM is really available to the user in Android Phones.
Please try "Free Memory" by coconuts on the market or the "free" command in Terminal to let me know the total RAM of your device so that I can understand how much is reserved for hardware operations.
Please also say which ROM are you using.
Thanks
poochie2 said:
Hello,
I'm trying to fill a table useful to understand how much RAM is really available to the user in Android Phones.
Please try "Free Memory" by coconuts on the market or the "free" command in Terminal to let me know the total RAM of your device so that I can understand how much is reserved for hardware operations.
Please also say which ROM are you using.
Thanks
Click to expand...
Click to collapse
bit confusing how devices with 768mb ram have only 300mb free ram on boot.... 400mb+ ram already used by android (+sense)
then imagine a few years back devices had/still have 256mb ram..
olyloh6696 said:
bit confusing how devices with 768mb ram have only 300mb free ram on boot.... 400mb+ ram already used by android (+sense)
then imagine a few years back devices had/still have 256mb ram..
Click to expand...
Click to collapse
Some is for caching and used ram also means that it is used for a good cause but I think that android uses too much RAM, maybe it's a bit related to using Java... I cannot believe that very simple widgets eat 10-12 MB of RAM so easily.
The ram is supposed to be taken up. It allows programs to start really fast(normally). This is normal. The programs in memory are based upon what you use. Available ram is wasted space. I generrally only have ~100mb free and have 512mb total. My phone never slows except when a dev does not implenent a listview correctly. As for Widgets with big ram req that is also a developer thing.
Sent from my Incredible using Tapatalk
wow! 12mb for a widget?!
yeh i understand it runs in the background, but if you use task killers you gain more ram back... the free ram ensures better performance though? it isnt 'wasted' is it?
do htc widgets generally use alot of RAM?
olyloh6696 said:
wow! 12mb for a widget?!
yeh i understand it runs in the background, but if you use task killers you gain more ram back... the free ram ensures better performance though? it isnt 'wasted' is it?
Click to expand...
Click to collapse
it's not
android have it's own internal task killer and there is no need to install additional apps to manage RAM and keep free memory for... for what? system knows how much free mem is needed to run and will kill processes when needed.
and if you close app with task killer and then would want to run it again, it will actually take more time than if it would be kept in RAM.
deadwilder said:
it's not
android have it's own internal task killer and there is no need to install additional apps to manage RAM and keep free memory for... for what? system knows how much free mem is needed to run and will kill processes when needed.
and if you close app with task killer and then would want to run it again, it will actually take more time than if it would be kept in RAM.
Click to expand...
Click to collapse
I generally agree with you, but my heavy usage of android shows me that things can get really slow even on my oced G2, when the available ram gets under 40 things get messy, increasing the lowmem limit saved me a bit but I aim for a 768 MB minimum for my next phone.
a widget takes 12mb of RAM because of the heap size of the way android OS is setup. it assigns 12mb of RAM regardless of whether that widget needs it or not. check each process, every one shown in system panel will be a minimum of around 12mb or so, even something that is only 75k. just the way android works.
RogerPodacter said:
a widget takes 12mb of RAM because of the heap size of the way android OS is setup. it assigns 12mb of RAM regardless of whether that widget needs it or not. check each process, every one shown in system panel will be a minimum of around 12mb or so, even something that is only 75k. just the way android works.
Click to expand...
Click to collapse
That seems a bit uncomfortable to me
i personally think that it could be changed better by removing some apks or in other ways to reduce something
In my opinion it is nonsense that 1-4 MB stuff must reserve a minimum of ~12 MB of precious RAM. In this way we just lose resources that would be better used for actual data.
Sent from my HTC Vision using XDA App
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