Related
To all the ROM cooks and expert,
I have a quick question regard the TOTAL amount of the RAM available in a ROM. I tried many new and old roms in this forum and I found one general conclusion. That is generally for all the roms (except the one with UL, Throttle Laucher, or SPB shell loaded), the amount of used RAM after a reboot is about the same, about 23 ~ 24 MB. However, what make the amount of free RAM available depends on the amount of TOTAL available RAM. This is my question, how come in some roms, there is about 52 MB available while some only have about 47 MB available. As you can see, the difference is about 5 MB, which is a good amount? Thanks
The total available RAM has to do with how big the pagepool is, how much is dedicated to the kernel, etc. The free RAM has to do with what's running in the background (programs, services, etc.)
ivanmmj said:
The total available RAM has to do with how big the pagepool is, how much is dedicated to the kernel, etc. The free RAM has to do with what's running in the background (programs, services, etc.)
Click to expand...
Click to collapse
I know to get more free ram, we can disable startup services and some background programs, but can we get more TOTAL available ram? I should ask this question up front. Our device, Herald or Wing, have 64 Meg of RAM, even with your JUSTME, the maximum it shows in "Device Information" is about 52 Megs. Where is the remain 12 Megs go? Can you tell me more details about it. Thanks
live4nothing said:
I know to get more free ram, we can disable startup services and some background programs, but can we get more TOTAL available ram? I should ask this question up front. Our device, Herald or Wing, have 64 Meg of RAM, even with your JUSTME, the maximum it shows in "Device Information" is about 52 Megs. Where is the remain 12 Megs go? Can you tell me more details about it. Thanks
Click to expand...
Click to collapse
I would think it would be for the OS software but I could be wrong.
speoples20 said:
I would think it would be for the OS software but I could be wrong.
Click to expand...
Click to collapse
Thanks. If it is for the software, then it should reside in the ROM. RAM is for anything that is running, currently or background. What I don't understand is that papa's newest RC6, Open Touch 6.5, and PDA viet's most updated ROMs they all have the same OS build (at least I believe they are), but the TOTAL available ram is different on each ROM. I am trying to build my own rom and just try to learn many thing as possible. Thanks
The "missing" RAM is taken by the XIP (kernel and such) and various other things like the pagepool. If these guys ran from the ROM, the device would be extremely slow.
Hello guys
I already used the search and looked around on the internet using google and ecosia... but it didn't help me... everytime i am looking for the answer to my question: "HTC says that the touch pro has got 288 MB of ram but there are only displayed 193 MB and my free memory is about 65 MB (used 128MB)" i only find some roms that say that they have a lower pagepool... but that does not help me in finding a solution to my problem that i can't access the complete ram...
is there any workaround for this issue? a classmate found a rom for his touch hd2 which solved the same problem as mine but on his hd 2... now i ask you for a solution on the touch pro.. please help me ^^
i think you didnt think about the fact that the OS needs ram too ... but you can try ROMs without manila that spare ram; which ROM do you actually have?
I'm using the latest energy rom, its all fast and very smooth animations.. really great :]
but no i think you didn't understand me... the hardware ram is 288MB according to HTC. The memory manager shows me that there is in total only 193 MB available. 128 MB of these 193 MB are used... the rest is unsused memory... now what is about the rest of the 288 MB ?
the osram usage is included in the 128MB if you trust the task manager ^^
so what is my phones problem? are there maybe some limitations that can be solved with some registry changes? on windows vor PCs you can disable some parts of the ram that they are not used... can this be a possible problem on my phone? when I was using the O2 branded original rom there were 212 MB usable 80MB used and 132MB free... i really can't imagine why ._.
ok, i see, but what about the memory that is needed to store the files that will be used restore the files after you do a hardreset?
Do you know nue storage manager? Try it and look, how much drives you have installed in your memory... which you dont have in normal use
do you know the difference between ram and rom? operating systems are always installed on roms and the ram looses its data during a hard reset.
audiocore said:
the hardware ram is 288MB according to HTC. The memory manager shows me that there is in total only 193 MB available. 128 MB of these 193 MB are used... the rest is unsused memory... now what is about the rest of the 288 MB ?
Click to expand...
Click to collapse
Yes, hardware RAM is 288 MB. In your case (with Energy ROM) 95 MB of RAM is used by the OS itself, so you have only 193 MB RAM available. You should know that the rest (in your case 193 MB) depends on the ROM cooker. Energy ROMs are known for not being RAM friendly, actually NRGZ28 stated once that he doesn't care for free RAM. That is the reason you have only 65 MB of free RAM. For example I'm using CRACING ROM and I have about 110 MB of free RAM after reboot, if Sense 2.1 is enabled. If I disable it, I have about 130 MB left. When I was using offical HTC ROM, I had more than 150 MB of RAM - that is with all today plugins (TF3D for example) turned off. Of course, if I disable HTC dialer (that has a video dialer and other options) and switch to ordinary WM dialer, I can free even more RAM. Pagepool is also very important - it is a special area of memory reserved for loading apps into from ROM. I think that the default pagepool is for Raphael 12 MB (that means 12 MB less RAM), but most of the cooks sets pagepool to 20 MB or more - that means 20+ MB of RAM used for faster loading of apps. That is why your phone is so fast with Energy ROM - it has a veeery large pagepool, but you have very little free RAM because of that.
So, to make things simpler, most of the RAM is used by the OS, GPU, TF3D/Sense/Titanium/SPB Mobile Shell/some other UI app, pagepool, dialer, other background services/processes etc. So you just have to decide what ROM to use - there are some ROMs (like yours current) that are very bad for RAM, but there are others with 120 MB+ or even 150+. You can also cook your own ROM and maybe gain 180 or more free RAM.
pilgrim011 said:
Yes, hardware RAM is 288 MB. In your case (with Energy ROM) 95 MB of RAM is used by the OS itself, so you have only 193 MB RAM available. You should know that the rest (in your case 193 MB) depends on the ROM cooker. Energy ROMs are known for not being RAM friendly, actually NRGZ28 stated once that he doesn't care for free RAM. That is the reason you have only 65 MB of free RAM. For example I'm using CRACING ROM and I have about 110 MB of free RAM after reboot, if Sense 2.1 is enabled. If I disable it, I have about 130 MB left. When I was using offical HTC ROM, I had more than 150 MB of RAM - that is with all today plugins (TF3D for example) turned off. Of course, if I disable HTC dialer (that has a video dialer and other options) and switch to ordinary WM dialer, I can free even more RAM. Pagepool is also very important - it is a special area of memory reserved for loading apps into from ROM. I think that the default pagepool is for Raphael 12 MB (that means 12 MB less RAM), but most of the cooks sets pagepool to 20 MB or more - that means 20+ MB of RAM used for faster loading of apps. That is why your phone is so fast with Energy ROM - it has a veeery large pagepool, but you have very little free RAM because of that.
So, to make things simpler, most of the RAM is used by the OS, GPU, TF3D/Sense/Titanium/SPB Mobile Shell/some other UI app, pagepool, dialer, other background services/processes etc. So you just have to decide what ROM to use - there are some ROMs (like yours current) that are very bad for RAM, but there are others with 120 MB+ or even 150+. You can also cook your own ROM and maybe gain 180 or more free RAM.
Click to expand...
Click to collapse
Great comment! Don't forget that the Radio will also use up some memory and especially with the HD2 there seems to be a Radio (original t-mobile) which uses almost 12 MB less than others.
However, what is your problem? You are concerned about battery life (keeping all that RAM happy and addressed) or you have a specific application which wont run. I didn't check the latest NRG ROMs but he ran pagepools up to 26 MB. It's one of the first things I check with a tool called pagepool changer. I adjust mine to 16 meg which is/was supposed to be the sweet spot for the Raphael/TouchPro and never had any problems, speed or memory issues.
tyguy said:
However, what is your problem? You are concerned about battery life (keeping all that RAM happy and addressed) or you have a specific application which wont run.
Click to expand...
Click to collapse
If the question is adressed to me, and not OP, I need at least 90-100 MB of free RAM because I heavily multitask. That is the main reason for being WinMo user. Besides, ROMs with low RAM are usually battery hungry.
pilgrim011 said:
If the question is adressed to me, and not OP, I need at least 90-100 MB of free RAM because I heavily multitask. That is the main reason for being WinMo user. Besides, ROMs with low RAM are usually battery hungry.
Click to expand...
Click to collapse
My answer was addressed to both. I also multitask though mainly Word, Excel and chat and as long as I don't open iGO all is running well (and you don't multitask while driving anyway ).
Let me check how much free RAM I have. ROM is in my sig, modified the PP from 26 MB (NRG's default) to 18 MB, Manila 2.5 with added Program Tab and Max Manila 2.7SE fullscreen on top. As you see I run the xperia X2 task manager because I too like to know what's left in RAM.
The screenshot is after ~ 4 days after the last boot "active sync'd"
tyguy said:
I also multitask though mainly Word, Excel and chat and as long as I don't open iGO all is running well (and you don't multitask while driving anyway ).
Click to expand...
Click to collapse
Well, I do multitask while driving. For example, iGo is running along with browser. When I need informations about traffic on main intersections (from the video cameras in my city), I open the link for that particular intersection via browser and then Streaming Media plays that clip. In the meantime iGo is running in the background of course. Lot of RAM is required for these tasks. And what if someone calls me - the dialer is also RAM hungry... Besides, often I use GPS whilst walking. This is just an example - like I said, I'm a heavy multitasker.
humm okaaay... but on my older eten glofiish x650 with only 64MB of ram I had about 24MB of free ram though windows mobile 6.5 (only tried it out ) so windows mobile can be 40MB small... and although it seems to run very well...
humm what do you mean with radio? the music radio or something like gsm radio module for windows mobile? (sry 4 my comprehension issues but i'm from germany ^^)
talking about the radio rom, which can be updated / changed like the OS and make it possible to get better phone reception or gps or ...
audiocore said:
humm okaaay... but on my older eten glofiish x650 with only 64MB of ram I had about 24MB of free ram though windows mobile 6.5 (only tried it out ) so windows mobile can be 40MB small... and although it seems to run very well...
humm what do you mean with radio? the music radio or something like gsm radio module for windows mobile? (sry 4 my comprehension issues but i'm from germany ^^)
Click to expand...
Click to collapse
I really think that you should read XDA Wiki, as much as humanly possible, in order to understand basic things about WinMo. Cheers, mate.
how come there are different free ram under running apps and setting>about phone??
which one is real or accurate?
i m using cm7 v.7.0.2
thanks guys
anyone can help me??
Only 384 MB
I prefer saying that Nexus S only had 384MB of RAM.
i can see that on my mem info of CM7 ROM only 345MB.
384 MB (real/physically) , 345MB (system read).
I can feel in true HD games, i used to use DeLL streak and playing Eternal Legacy HD, it cannot run while background apps running untill i kill all task and give me free RAM around 312MB . THe the game start perfectly.
On my Nexus S the game cannot run, just kick back to home screen, its like insufficient RAM ( it was not force closing ).
So i assume nexus S only has totally 512MB - 128MB = 384MB. CMIIW
mine says 345mb total in the about phone and 156mb free but i have never had a problem while loading a game... what game is it that is closing itself??
maybe i can try running it and see what happens...
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
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