4.4 and RAM - Nexus 7 General

Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app

butler0607 said:
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
I think so, the spare RAM should make the ROM about 3 times more spare RAM, and quite fast.

butler0607 said:
Sorry if this sounds like an obvious question but I'm a bit confused! If KitKat is optimised to run on 512mb apps, doesn't mean that on devices like ours with lots if RAM, the performance will increase dramatically thanks to a lot of spare RAM? Also, to me, if you're running such low mb ROM 2GB of RAM seems a bit wasteful (I.E. you'll be paying for a function with little benefit?) Is thus about right or am I way off the point?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Short answer.. your way off..
Long Answer..
The big change is that the system now degrades gracefully on low resource devices.. so things like animations and textures are reduced to maintain the systems overall performance even on low resource devices.. versus say jellybean and ICS which simply tried to run regardless even on the original G1.. bringing the entire system down to a crawl (this is a vastly oversimplified version of a portion of what is going on in 4.4 and is not meant to be exhaustive explanation)
The second part of your question is why I want to strangle every marketing person from the beginning of time.. just because the system CAN operate with less ram does NOT mean that it is not USING all of the ram in your device.. the system will invariably use up as much as it can get its hands on (and still try to grab some more!)

OK, I think I get it! Thanks for the help
Sent from my HTC Desire C using xda app-developers app

Improved memory management should (in theory) also help the Tegra 3 chip since it has slow single-channel ram.

Related

[Q] Too little RAM?

I've seen other phones that will be released this Q1 or Q2 having 1GB of RAM whilst the Optimus 2X only has 512MB.
I myself have kind of got the feeling that 512MB's would be enough and that 1GB is unnecessary, but I would like your opinions, and maybe an explenation to why 512MB's would be enough?
Since Atrix won't be released in Sweden that pretty much leaves it to Optimus 2X or the Galaxy S2, but the S2 will probably be like 200 dollars more. Would that really be worth the money RAM-wise (other differences doesn't matter that much to me)?
I'm of the mind that 512MB will be fine for the forseeable future. If you consider that the most demanding apps are typically games, and the most impressive games (since GameLoft, Epic etc have signed on with nVidia...) will be developed to Tegra 2 specs, I can't imagine those Tegra 2 specs would preclude running on 512MB of RAM. Following that assumption, by the time 512MB of RAM isn't enough, you will probably be due for an upgrade anyway.
I'm starting to think that the only reason the Atrix has 1GB is because the WebTop mode runs well over 512MB in typical operation. Then, of course, the Galaxy 2 has a gig so that it doesn't look inferior on paper.
Just my conjecturous 2 cents.
Sjael said:
I'm of the mind that 512MB will be fine for the forseeable future. If you consider that the most demanding apps are typically games, and the most impressive games (since GameLoft, Epic etc have signed on with nVidia...) will be developed to Tegra 2 specs, I can't imagine those Tegra 2 specs would preclude running on 512MB of RAM. Following that assumption, by the time 512MB of RAM isn't enough, you will probably be due for an upgrade anyway.
I'm starting to think that the only reason the Atrix has 1GB is because the WebTop mode runs well over 512MB in typical operation. Then, of course, the Galaxy 2 has a gig so that it doesn't look inferior on paper.
Just my conjecturous 2 cents.
Click to expand...
Click to collapse
Thanks for your reply! I also thought about the RAM being for the WebTop but then Samsung released the S2 lol.. I would probably agree with you that 512MB will be enough in at least the coming year or so, hell, you can almost run a game like World of Warcraft on 512MB RAM.
Maybe Motorola and Samsung are just putting in hardware that is ahead of the future to atract the customers that want 'the best'. Of course, they are probably slightly better but from what I understand it is kind of hard to fill up 512MB RAM which they also say in Anandtechs review of the Atrix.
http://www.anandtech.com/show/4165/the-motorola-atrix-4g-preview
If only LG could put in at least 768MB I wouldn't have to worry
Have to agree with Sjael about the 512MB of RAM in the Atrix being for the laptop dock. In that preview you posted in the benchmark tests the optimus came out on top of the atrix pretty much every time. So don't let the 512 MB of RAM detour you!
I would not mind 512MB RAM(Actually, you can use only 372MB of ram because of the android system)
512MB ram is not that small, and there is no app that needs more than 512MB.
I'm using Optimus 2X, but 512MB RAM was okay
pokerfake said:
I would not mind 512MB RAM(Actually, you can use only 372MB of ram because of the android system)
512MB ram is not that small, and there is no app that needs more than 512MB.
I'm using Optimus 2X, but 512MB RAM was okay
Click to expand...
Click to collapse
'Okay' doesn't sound too convincing. Could you tell us about the phone in general? Are you satisfied, how is the battery life etc?
Battery time is simuliar with Samsung Galaxy
LG home sometimes reset after I play some heavy 3D game. I think that its because of RAM, but this problem does not happen if you change your home program
Sent from my LG-SU660 using XDA App
pokerfake said:
Battery time is simuliar with Samsung Galaxy
LG home sometimes reset after I play some heavy 3D game. I think that its because of RAM, but this problem does not happen if you change your home program
Sent from my LG-SU660 using XDA App
Click to expand...
Click to collapse
What about gps ?
GPS is waaay better than Samsung Galaxy S
Sent from my LG-SU660 using XDA App
pokerfake said:
Battery time is simuliar with Samsung Galaxy
LG home sometimes reset after I play some heavy 3D game. I think that its because of RAM, but this problem does not happen if you change your home program
Sent from my LG-SU660 using XDA App
Click to expand...
Click to collapse
The LG launcher doesn't look too attractive anyway so i'll probably go for LauncherPro
pokerfake said:
GPS is waaay better than Samsung Galaxy S
Sent from my LG-SU660 using XDA App
Click to expand...
Click to collapse
Really ? Oh, this is a great news !
1GB is better than 512MB
but....... i think 512 is enough, also
Well we now have some empirical evidence...
The +64MB RAM kernel gives back 64MB to the user and it makes a *huge* difference to performance in general day to day use for me. I no longer need to use minfreemanager and my launcher and background apps hardly ever get shut down by the system now.
I used to be of the mind that 512 was enough (=372) but with +64 (=436) there's a world of difference.
So, in my experience 512 is a constraint.
Its not the 512mb itself being the limit here, its the way these 512mb are used and how Android is configured to manage the memory by the manufacturer - but yes more ram to work with are allways a benefit.
512mb is plenty in the HTC Desire which default has about 440mb for the user, while the LG only has 372mb (more ram allocated for video than the Desire perhaps ?)
Furthermore the default minfree setting in the Desire is configured to allways leave 140mb free, while the LG is default configured to only leave around 80mb free.
This cause the LG to run low on memory, needing the system to free up memory by shutting down apps that are preloaded, faster and more often than on the Desire.
The extra 64mb you free with the other Kernel can be configured either as more ram for preloadet apps or as just free ram - depending on how agressive you set the minfree setting. The result you get will be a combination of this - if minfree are still set to 80mb then the 64mb are just used to preload more apps, which you will feel as a benefit if switching to one of these preloaded apps, but wont feel as a benefit if you need to run an app that use up more than the free 80mb and which hasnt been preloaded. On the other hand you could divide it and set the minfree setting to 110 and let the rest 34mb be used to preload apps in, that way a running app could use more ram before it would need to shutdown preloaded apps.
I cant say which setting would be the best overall - but for certain the configuration of the memory works better in the Desire than the one in the LG - despite both having 512mb ram

Why 512MB of RAM means no Bionic for me

I've seen a lot of discussion on various Android/Droid forums on the web over the past month or two about the Bionic, and it having 512MB of RAM. A lot of people don't seem to mind, and some people have even said it doesn't matter because it's DDR2, which is faster than regular DDR.
Well, 512MB of RAM is not enough for a dual-core phone you plan to use for 2 years or more. Here's why, in a rather lengthy post that I also put on MyDroidWorld the other night. I've been on the XDA forums for a long time, though I don't post very frequently and I'm curious to see what people will think of my admittedly long post. So, here is why I think people should think long and hard about whether to buy the Bionic when it does come out, assuming it still ships with 512MB of RAM.
Caching.
Ok - let me explain. The single most important factor in performance of a computer is having enough RAM. When a computer runs out of RAM, it starts to use what's called a page file. It's basically a file on your hard drive that acts as additional RAM. Now, DDR3-1600 speed RAM transfers data at 12.8 gigabytes per second. Phenomenally fast. It also has a reaction time of around 5 nanoseconds, also ridiculously fast. When your operating system has to start using the page file because the physical RAM is full, the performance hit is EXTRAORDINARY. Even the best hard disk drives (not counting SSDs) like the latest Raptor from Western Digital cap out at around 155 megabytes per second for reading and writing, and it has a peak latency of 7 milliseconds for reaction time. 1 nanosecond is 1 million milliseconds, which makes the DDR3 RAM over a MILLION times faster reacting than the hard drive, and the transfer rate of the RAM over 80 times faster than the transfer rate of the hard drive.
In real-world terms, it's like you're talking about an ant versus a Porsche 911 Turbo. Most old computers that have long pauses or hang for several seconds doing even basic tasks, it's because they don't have enough RAM and it's caching stuff between the hard drive and the RAM.
Now, whenever Android runs out of RAM, (same with any operating system) it has to start using its page file, which means it starts using this monstrously slow flash memory as RAM. It's like merging onto a freeway that is gridlocked with traffic when you were going hundreds of miles per hour. The flash memory is a lot slower than the Raptor hard drive for data transfer rates, but it has a read time a lot faster; the best-performing ones are generally under 1 microsecond. 1 microsecond is a thousand times slower than 1 nanosecond. The write times are closer to hard drives, though; generally less than 1 millisecond, so like 10x faster than a hard drive but still 100,000 times slower reaction time to writing data than the RAM is.
What this means is, when your permanent storage is flash-based, it has a much faster reaction time than a hard drive but it's still dog-slow compared to RAM; so when Android runs out of RAM, it caches to the page file on the flash memory, and you'll have the same slowdown effect as you do on an old POS computer, but it's not as noticeable because flash memory reacts faster than disk-based hard drives.
The point of all of this is that, 1GB of DDR1 memory on a phone is FAR better than 512MB of DDR2 memory. The 1GB will prevent you from hitting that metaphorical brick wall of caching data to your flash memory when the 512MB won't. We already use 400MB, or more, of our 512MB of RAM on our existing phones just by turning it on and having a couple of widgets/services in the background above & beyond the stock ones. How do you expect to take advantage significantly higher-end applications and games, which also means (for games, primarily) that they take up more RAM, as well?
You can't have higher-quality graphics without needing more RAM, so when that new version of Angry Birds comes out this fall or something that requires two cores and looks amazing, but uses 250MB of RAM to run instead of the 80MB or whatever the regular one uses now, what do you think has to happen? That's right. Android has to cache that much extra data to your flash memory so it can unload it from the RAM, freeing the necessary space to load Angry Birds HD. This causes more of a delay as it's writing data, and will cause extra choppiness, etc. Another thing to keep in mind is that, as resolutions increase, so do the texture sizes for all applications and widgets that you use, assuming they support the new resolution. More size needed, which takes up more space in RAM.
Don't be fooled. When truly good and proper dual-core benchmarks come out, 1GB RAM dual-core phones will spank their 512MB RAM dual-core brethren for real-world performance in games, and other high-memory applications. Also, excessive caching greatly increases the chance of flash memory going bad. Not a common occurrence if it was fine when shipped, but still something to think about.
So, in summary, even though the performance hit from caching to flash memory isn't as bad as caching to hard disk drives, it's still a tremendous slowdown and it will matter for dual-core phones way more than for single-core ones. The average amount of RAM installed on dual-core desktop computers from Dell/HP/etc. was significantly higher than what the average was for the previous single-core generations were, and there are reasons for that. Primarily, the same reasons I just outlined. In simple terms, faster processors can do more things, which necessarily requires more RAM.
Sorry for the wall of text, I tried to be more concise but it kind of got away from me. I'm not buying a Bionic because it has 512MB of RAM. After owning it a year, it'll be having performance issues on top-end dual-core-required games that run just fine on phones like the Atrix.
I'm sorry because I know this is probably going to come across the wrong way, but WOW, you spent a lot of time writing that up, and too much time for me to read it alll, especially considering Motorola has pulled back on the Bionic and it's receiving "enhancements". I guess what I'm saying is why all the speculation/conjecture until we know the revised specs? Maybe it'll land with 8GB of DDR 6 RAM.
I'm hoping Motorola gives Verizon a phone that is higher end than the Atrix. Afterall Verizon has done much more than ATT in the way of supporting Moto..when they needed it. Anxious to see what Big Red winds up with.
Sent from my ERIS using XDA Premium App
I disagree that ram is the single most important factor of performance of a computer.
hard drives are the biggest bottleneck in a computer. this is why I use a vertex 3 ssd.
Sent from my PC36100 using XDA Premium App
gemro311 said:
I'm hoping Motorola gives Verizon a phone that is higher end than the Atrix. Afterall Verizon has done much more than ATT in the way of supporting Moto..when they needed it. Anxious to see what Big Red winds up with.
Sent from my ERIS using XDA Premium App
Click to expand...
Click to collapse
I concur, really hope VZW pushes for a premier device
I disagree. Android isn't expanding as an OS at some breakneck pace and 512MB is definitely suitable for the near future. 1GB is absolutely not necessary for great performance in a phone. RAM is a bottleneck, but it is not something that magically allows for better performance if the device isn't hitting the pagefile anyway.
The way that Android manages applications will allow 512MB phones to be relevant for some time. The Bionic will be a solid phone for the next year, but there will always be something bigger and better next year. Phones aren't future-proof.
I was just checking out this thread and wanted to say maybe the reason that the atrix comes with 1gb of ram is because of the extra contraption that you can buy along with. It looks like a netbook but is not very well performing and who would even care to rely on it for anything I don't know.
gemro311 said:
I'm hoping Motorola gives Verizon a phone that is higher end than the Atrix. Afterall Verizon has done much more than ATT in the way of supporting Moto..when they needed it. Anxious to see what Big Red winds up with.
Sent from my ERIS using XDA Premium App
Click to expand...
Click to collapse
I certainly hope Motorola makes the required improvements, but you also need to keep in mind Verizon approves and in many if not all cases specs the phones they want. They chose the specs, they had to live with the specs. I think once they saw what was coming they figured it was no longer premiere and wanted changes made.
Regardless of why its been pulled back the fact that it was is good, but if its going to take 4-5 months to get it out the door they should have just scrapped it altogether.
E30kid said:
I disagree. Android isn't expanding as an OS at some breakneck pace and 512MB is definitely suitable for the near future. 1GB is absolutely not necessary for great performance in a phone. RAM is a bottleneck, but it is not something that magically allows for better performance if the device isn't hitting the pagefile anyway.
The way that Android manages applications will allow 512MB phones to be relevant for some time. The Bionic will be a solid phone for the next year, but there will always be something bigger and better next year. Phones aren't future-proof.
Click to expand...
Click to collapse
Well, wait for Ice Cream and we'll see. Since the future Android version will also run in tablets, it is likely that it will have huge memory requirements.
By the way, my Acer Liquid A1 can't be officially upgraded to Froyo because it only has 256Mb. Later Liquid models with 512Mb are upgradeable. At the time I bought it, 512Mb seemed unnecessary because the Nexus One operating system only supported 256Mb, having the other 256Mb wasted. This was only 12 months ago...
galaxyjeff said:
I was just checking out this thread and wanted to say maybe the reason that the atrix comes with 1gb of ram is because of the extra contraption that you can buy along with. It looks like a netbook but is not very well performing and who would even care to rely on it for anything I don't know.
Click to expand...
Click to collapse
I think you are on to something here. I think I read somewhere that the atrix only uses 512 mb when not connected to the dock. I have the inspire which has 768 mb, and I came from the captivate which was 512 mb, and I done know if is the ram or what but this phone performs way better than the captivate. Even when I bought the inspire, right out the box stock, preformed much better than a captivate overclocked with an ext4 filesystem kernel. Not that this is empirical evidence, but hey.
Sent from my HTC Desire HD using XDA Premium App
cryptiq said:
I'm sorry because I know this is probably going to come across the wrong way, but WOW, you spent a lot of time writing that up, and too much time for me to read it alll, especially considering Motorola has pulled back on the Bionic and it's receiving "enhancements". I guess what I'm saying is why all the speculation/conjecture until we know the revised specs? Maybe it'll land with 8GB of DDR 6 RAM.
Click to expand...
Click to collapse
I lol'd. But seriously 512 MB of RAM is more than enough... It's a PHONE not a high end desktop system. I play tons of games on my x2 and with alot of crap in the backround open, and I notice zero performance hits. If you are spending all day monitoring your RAM on your phone and trying to measure FPS loss, load time differences, etc. I suggest that you try to pick up a new hobby ASAP, OCDing will be the end of you. Best of luck!
Edit: I wouldn't worry about it either! Bionic probably won't come out anyways, and if it does, another phone with 1GB to satisfy your OCD probably will be out by then.
As of now, I feel ALL future top tier smart phones need to come equipped with at least 1GB of DDR2. The G2x, for example, will most likely have issues running a custom ice cream rom. And people will be upset.. especially after putting up with all of the other various problems that particular phone has.
OP, I don't agree entirely with your explanation of the use of caching by the OS - for all 3 major computer OSes, no matter how much excess RAM you have, they will start caching data to the hard drive, whether you like it or not. Obviously if you run out of RAM, it has to do so, but it'll even do it long before you've hit that cap - just because it determines an application has gone "inactive". Now I haven't read up on Android enough to know whether this is 100% true for it, too, but considering it's running a linux kernel, I would imagine so. So just like the 8GB of RAM in my desktop doesn't necessarily help for everyday computing needs, 1GB vs 512mb on the Bionic may not make a huge difference.
raptordrew said:
OP, I don't agree entirely with your explanation of the use of caching by the OS - for all 3 major computer OSes, no matter how much excess RAM you have, they will start caching data to the hard drive, whether you like it or not. Obviously if you run out of RAM, it has to do so, but it'll even do it long before you've hit that cap - just because it determines an application has gone "inactive". Now I haven't read up on Android enough to know whether this is 100% true for it, too, but considering it's running a linux kernel, I would imagine so. So just like the 8GB of RAM in my desktop doesn't necessarily help for everyday computing needs, 1GB vs 512mb on the Bionic may not make a huge difference.
Click to expand...
Click to collapse
i beg to differ
my captivate; even though its a single core...is still quite capable at most everyday tasks...only thing lacking is the RAM
my phone will slow to a crawl after entering twitter, switching to pulse and then going back to my homescreen....
not to mention my launcher keeps getting killed by android as it keeps running out of RAM
droid_does said:
i beg to differ
my captivate; even though its a single core...is still quite capable at most everyday tasks...only thing lacking is the RAM
my phone will slow to a crawl after entering twitter, switching to pulse and then going back to my homescreen....
not to mention my launcher keeps getting killed by android as it keeps running out of RAM
Click to expand...
Click to collapse
I have to lol at this one. Absolutely none of those issues have to do with amount of RAM. In fact the launcher problem has nothing to do with RAM at all.
Sent from my ADR6400L using XDA App
While I appreciate other people who have the same amount of passion for phones as I do, I just have two words to say about anyone saying phones with 512 mb ram will not get Ice Cream Sandwich. Nexus S.
Sent from my ADR6400L using XDA App
mb02 said:
I have to lol at this one. Absolutely none of those issues have to do with amount of RAM. In fact the launcher problem has nothing to do with RAM at all.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
it does as android keeps killing it to free up more RAM to use......
droid_does said:
it does as android keeps killing it to free up more RAM to use......
Click to expand...
Click to collapse
Yea the task manager is killing the apps to keep ram freed up, as in stopping unused processes etc. That's just the aggressive working of the management software that would run just the same if you even had 8GB of ram.
Sent from my ADR6400L using XDA App
timothymilla said:
While I appreciate other people who have the same amount of passion for phones as I do, I just have two words to say about anyone saying phones with 512 mb ram will not get Ice Cream Sandwich. Nexus S.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Remember when everyone thought Gingerbread would require a 1GHz processor as a system requirement, which was later debunked?
http://www.talkandroid.com/23041-so...ngerbread-update-due-to-1ghz-cpu-requirement/
Nobody can say what will and will not get updated for sure, although I will venture to say that it's HIGHLY likely the Nexus S will be getting 2.4, you're right.
zetsumeikuro said:
I lol'd. But seriously 512 MB of RAM is more than enough... It's a PHONE not a high end desktop system. I play tons of games on my x2 and with alot of crap in the backround open, and I notice zero performance hits. If you are spending all day monitoring your RAM on your phone and trying to measure FPS loss, load time differences, etc. I suggest that you try to pick up a new hobby ASAP, OCDing will be the end of you. Best of luck!
Edit: I wouldn't worry about it either! Bionic probably won't come out anyways, and if it does, another phone with 1GB to satisfy your OCD probably will be out by then.
Click to expand...
Click to collapse
512 mb is not enough for a dual core 4G phone it just isnt. the thunderbolt has 768 mb and its only single core and 4G and let me tell you it would be way faster with the 1024 mb of ram i cant imagine how laggy the bionic would be if you start doing anything with it! the 512 ram will be ate up in no time! i sure hope verizon reconsiders and adds more ram or i probably wont use this device as my daily phone either keep the thunderbolt with more ram which is sad cause it has been out for awhile now and the droid x also has 512 ram and it has been out for a year and they cant make improvements?? and they are going to want $299+++ for this phone ON CONTRACT! it better have more than 512 ram or it aint worth a lick! rip this phone open and put my own ram in it!

how much ram do we really have?

i thought the cappy had 512 mb of ram... why do all the roms have like 341? im confused >.< either i looked at 3 faulty spec sheets for the captivate or we arent utilizing the full ram potential for the captivate. would someone explain the truth on this matter to a captivate noob like me?
i could be wrong but i believe the 341 is available to use ram, while the rest is being used by the phone to function.
nehal51086 said:
i could be wrong but i believe the 341 is available to use ram, while the rest is being used by the phone to function.
Click to expand...
Click to collapse
that would make sense, but that makes the specs misleading... i traded my HD2 for a cappy because the spec sheet said 512mb of ram and the HD2 only has 411 available to the OS when running android from nand because the rest is dedicated to winmo only (which sucks massively), and i wanted more ram lol, guess i should have looked harder into things, but regardless the captivate is "better" in very many areas, but RAM is literally my deciding factor for so many things lately (like t-mobile with the sensation or sprint with the evo 3d, i would say evo 3d because it has 256mb or so more ram)
This question has been asked and answered several times....
the phone does have 512mb of ram. Like the person above me said the phones os and graphics take up a portion of the ram. All computers and smart phones work the same way.
As a side note android handles ram very well. You don't need to manage it at all by freeing it up. free ram is wasted ram as the os will have to load it back up anyways
Sent from my GT-I9000 using XDA App
crystalhand said:
This question has been asked and answered several times....
the phone does have 512mb of ram. Like the person above me said the phones os and graphics take up a portion of the ram. All computers and smart phones work the same way.
As a side note android handles ram very well. You don't need to manage it at all by freeing it up. free ram is wasted ram as the os will have to load it back up anyways
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i know this very well, free ram can be considered wasted ram, unless you need 200mb or so free for a tegra class game, but i think android handles ram awesomely to an extent but can be improved by implementing autokiller memory optimizer in a knowledgable and appropriate way that doesnt hurt optimizations android already has in place, zipaligning, increasing the dalvik heap size, etc... can all be done, im not asking about how android handles ram or anything, and im sorry i didnt know the question had been asked several times i am brand new to the captivate today, literally, and was doing not but seeking information i didnt understand or know, thank you for the explaination though i appreciate it, and im glad to know that my new captivate will utilize the left over 171mb of ram for something unlike my HD2 that couldnt access the last 100mb because it was designated to winmo only. i had an idea that was the case and i was just clarifying to myself because i kept reading rom changelogs stating "enabled more ram now 341mb available" or something along the lines of that and thought to myself "there should be more available already" lol
I honestly think 341MB is enough.
341 MB is alot. But something is taking all that up too. On a fresh boot, half of it is used, and I have 140~170 MB. Its even worse on GB. Most ive gotten is 100 MB free.
So if the half of the 341 plus the mysterious 171 MB that is nowhere to be found, I dont get whats using the other 171 that is not part of the 341. Lol confusing
Same happens to me. Who knows, lol
Sent from my GT-I9000 using XDA Premium App
I think its the user interface graphics, like scrolling quality is good because that ram is dedicated to things
like that
Sent from cyanogen mod 7

Less free RAM after v20 GB upgrade

Anyone encounter the same issue? Used to have around 180mb before upgrade. Now most times less than
100Mb
Sent from my LG-P990 using XDA App
Not less than 100MB but also less than with Froyo.
cheeese said:
Anyone encounter the same issue? Used to have around 180mb before upgrade. Now most times less than
100Mb
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Get a task manager and kill some tasks then, after killing tasks and only excluding stuff i need, eg. messenger app, music ect i get 205mb free ram and never go below 100mb.
I did still?at most 120 only.
Sent from my LG-P990 using XDA App
OMG guys, why don't people get this:
Free RAM is wasted RAM.
/thread
kiljacken said:
OMG guys, why don't people get this:
Free RAM is wasted RAM.
/thread
Click to expand...
Click to collapse
Because your phone slows down when it gets below 100mb, don't bother arguing that because i know from experience that my o2x slows down and becomes choppy when the free ram goes below 100mb, because there is so much crap stored in memory.
If i need something to run ill run it and leave it there and exclude it from task manager but other wise its no use.
Its also a huge battery drain to have so many apps running that you are not using so that's a pretty stupid statement...."free ram is waste ram" lol wtf...., your battery life must be really long.
As for OP, i suggest you install a better rom, i use topigigis 1.7 rom and after killing a bunch of tasks i get up to 205mb free, altho this gets less the longer it goes without a reboot, so try rebooting and hen killing some useless tasks and see what your ram level is at.
eraldo said:
Because your phone slows down when it gets below 100mb, don't bother arguing that because i know from experience that my o2x slows down and becomes choppy when the free ram goes below 100mb, because there is so much crap stored in memory.
If i need something to run ill run it and leave it there and exclude it from task manager but other wise its no use.
Its also a huge battery drain to have so many apps running that you are not using so that's a pretty stupid statement...."free ram is waste ram" lol wtf...., your battery life must be really long.
As for OP, i suggest you install a better rom, i use topigigis 1.7 rom and after killing a bunch of tasks i get up to 205mb free, altho this gets less the longer it goes without a reboot, so try rebooting and hen killing some useless tasks and see what your ram level is at.
Click to expand...
Click to collapse
Free ram is wasted ram. And taskkillers will only make you battery life worse if not some app is using all the cpu. The reason RAM is used by android is to keep apps preloaded, for better launch times. The built in task handler is all what is needed. My phone runs blazingly fast at all times, and I don't use a taskkiller.
yupe.. Mine is mostly below 100mb.. 70mb on average. but it's smoother than froyo with 140mb.. list of applications and files are faster to load and smoother.. so i have no complain at all.
I'm also experiencing the lower free memory in the default configuration with GB compared to Froyo. Although I'm not trying to get as much free RAM as possible (because I support the reasons given above for usage of the RAM, having apps in there doesn't mean that they're running) I'm still curious where the missing amount of memory went... Does anybody have any clue what was introduced or changed with GB that could use up about 70MB?
kiljacken said:
Free ram is wasted ram. And taskkillers will only make you battery life worse if not some app is using all the cpu. The reason RAM is used by android is to keep apps preloaded, for better launch times. The built in task handler is all what is needed. My phone runs blazingly fast at all times, and I don't use a taskkiller.
Click to expand...
Click to collapse
Oh really and what is your logic for thinking having no unused apps running will use more battery than having lads running.....you make no sense an have no logic or fact to back up such a ridiculas assumption.
Sent from my LG-P990 using XDA Premium App
kiljacken said:
Free ram is wasted ram. And taskkillers will only make you battery life worse if not some app is using all the cpu. The reason RAM is used by android is to keep apps preloaded, for better launch times. The built in task handler is all what is needed. My phone runs blazingly fast at all times, and I don't use a taskkiller.
Click to expand...
Click to collapse
Clearly you've been on cm7 so long you forgot how bad stock is..
Stock firmware for my phone was horrible and backgrounding was working for only seconds due to lack of ram, Opera would never background, always a new boot.
Cm7 > stock
Sent from my Optimus 2X using Tapatalk
I m on stock v20 ROM. Sometime my fone will b sluggish and it seems like e low RAM is causing it. Also wondering where e RAM went After upgrading.
use supercharger
Code:
http://forum.xda-developers.com/showthread.php?t=991276
And there's a bug in original stock kernel about memory management, horse power kernels are better for that.
Its not just about the rom your choosing its about the kernel, flash a good kernel and it will improve memory usage.
So does flashing custom kernel void e warranty and does it need rooting? Which is e best kernel for stock ROM v20?
Thanks
Sent from my LG-P990 using XDA App
cheeese said:
So does flashing custom kernel void e warranty and does it need rooting? Which is e best kernel for stock ROM v20?
Thanks
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Yes most of the time and Yes. Some providers accept phone customization in warranty, ask yours.
If you have v20L you only have Horse Power kernel (Neoblaze seems bootloop) + Power pack 7 (mandatory, orbootloop, see dedicated threads).
If I reflash my phone using one of the original images availabe and reset it, is there any chance for the provider to detect previous flash operations?
Striatum_bdr said:
Yes most of the time and Yes. Some providers accept phone customization in warranty, ask yours.
Click to expand...
Click to collapse
cheeese said:
So does flashing custom kernel void e warranty and does it need rooting? Which is e best kernel for stock ROM v20?
Click to expand...
Click to collapse
Befor i flashed hp sr2 i had 70 to 90 mb free ram now i had 130 to 150 free ram and my baterry seems better.
Sent from my LG-P990 using XDA App
I'd tend to relate the better battery life to the new kernel than the increased free ram. I'm on RC9 (w. PP7, no init.d-scripts) and my LGOS reaches almost two days of battery standby with ~50-60MB free RAM.
luka2858 said:
Befor i flashed hp sr2 i had 70 to 90 mb free ram now i had 130 to 150 free ram and my baterry seems better.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse

Jelly Bean eats all of ram!!! Severe Ram problem

Oh, after using jelly bean for 3 days, i noticed that it eats all of Ram, only 60-110 MB free!!!!
And this cause very slow downs and FC alot,
While on ics there is about 200-250 MB Free!!! With the same apps
Is this bec. Of beta, running, and freezing all bloatware and the same aetup in every aspect
, is 1GB of ram isn't enough now days!!!
Again, i tried to use swap file using various methods with no success due to kernel support, is there any kernel or method to have working swap, or is there any workaround to have some thing similar to swap.
Sent from my GT-N7000 using xda premium
The note actually only has 800mb, so it's not even a gig.
well ram works differently on android then on windows pc, if its full it doesnt necessary mean that's why device is slowed down. Memory works differently.
Secondly jb, you are using now is not for everyday use. So you are bound to run into issues like this one. Also there is a memory leak in current builds. Which means that JB doesnt do that, but the current build does that because of a bug.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
well ram works differently on android then on windows pc, if its full it doesnt necessary mean that's why device is slowed down. Memory works differently.
Secondly jb, you are using now is not for everyday use. So you are bound to run into issues like this one. Also there is a memory leak in current builds. Which means that JB doesnt do that, but the current build does that because of a bug.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yes i know that full ram may not cause slow downs, well it will slow down only when riched critical value and cause FCs , but you say that this problem in JB is due to beta stage, so this is good, so we have to wait for fully working build or at least stable enough to run system without FCs or slowdowna
Sent from my GT-N7000 using xda premium
Yep definately.
I guess it takes extra clean installs with prenightly roms.
Maybe, because you got this far you can get comfortable with logfiles and troubleshooting. Try to get to the root cause of the issue. You might be able to contribute there.At this point if I knew how, I'd help you.
Sent from my GT-N7000 using Tapatalk 2
little-vince said:
The note actually only has 800mb, so it's not even a gig.
Click to expand...
Click to collapse
Is that true? I don't think so. I think it's how it's allocated and counted. Like when you go buy a 1TB drive, you only have access to 931GB. It's how it's formatted and allocated.
Probably the same with Android with memory allocation or something like that. It's false advertising to say "It has 1024MB of RAM" when they actually only include 800. 800 is accessible, but there's probably 1GB in there.
zkyevolved said:
Is that true? I don't think so. I think it's how it's allocated and counted. Like when you go buy a 1TB drive, you only have access to 931GB. It's how it's formatted and allocated.
Probably the same with Android with memory allocation or something like that. It's false advertising to say "It has 1024MB of RAM" when they actually only include 800. 800 is accessible, but there's probably 1GB in there.
Click to expand...
Click to collapse
There almost certainly is 1GB of RAM in there, but the graphics processor needs some of it to do it's job, say probably 128MB. Then just like the PC there are other other parts of the device that need to have blocks of memory to do their jobs, and the kernel and other core OS will probably snarf some memory to do what they need to do.
Voila, 1GB of RAM immediately reduced to 500-800MB of actual "usable" RAM.
Yup, the 1gb is a lie.. galaxy note has the same amount of ram of desire hd
Sent from my GT-N7000 using xda app-developers app
LoVeRice said:
Yup, the 1gb is a lie.. galaxy note has the same amount of ram of desire hd
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
No dear, desireHD has 786 MB BUT ONLY about 600 MB usable, the same story as note and every android device
Sent from my GT-N7000 using xda premium
evaworld said:
No dear, desireHD has 786 MB BUT ONLY about 600 MB usable, the same story as note and every android device
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Based on every nand device out there, ssd, emmc, all of them allocate sectors to general use.
Sent from my GT-N7000 using xda premium
Can part of internal sd or ext sd become an extended ram or something?
Would that make the device any faster?
Sent from my GT-N7000 using xda app-developers app
fr3ker said:
Can part of internal sd or ext sd become an extended ram or something?
Would that make the device any faster?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes it can.
No that won't make it any faster. In fact, it will make it slower.
The way Android works is, it says "the kernel says I need X amount for gpu, X amount for sound, X amount for the OS".
And then it allocates a certain threashold and says "okay this much I'm keeping free".
Then it says "these functions of the OS aren't used often, I'll leave them out".
Then it says "okay so I've got extra ram room, I'm going to fill them up with Apps".
Why does it work this way?
It based on Linux, RAM is shared dynamically.
What does this mean?
A bloated kernel and OS will use more RAM for itself.
Why does it leave free ram?
In case it needs to execute a function that's not used often or is memory intensive (eg Browser).
Why does it store Apps?
So that its readily available. They just pop open. Or resume from last state.
...okay, so what does this mean about my Free RAM "issues" with Jelly Bean?
It means that you are uneducated. It means Jelly Bean, or the specific setup you have either is more bloated than your previous setup OR it has a low "free ram allocation" setting. Solution? There is no problem, though you can trim down the ram allocation and kill off some memory things (apps, hidden background tasks) you can increase the amount of Free RAM, but its more likely to slow down the system. Remember, Jelly Bean builds are still Alpha/Beta stage, so they can/do have memory leaks.
Another point I should mention:
OS RAM use increased a lot from 1.6 -> 2.1
OS RAM use increased from 2.1 -> 2.2
OS RAM use increased a lot from 2.2 -> 2.3
OS RAM use increased a lot from 2.3 -> 4.0
< I haven't checked JB, but I'm willing to bet its increased from ICS, even if slightly >
This is Android, not Windows. Its behaves differently and has different symptoms. A quick Google search could've answered your questions.
Kangal said:
Yes it can.
No that won't make it any faster. In fact, it will make it slower.
The way Android works is, it says "the kernel says I need X amount for gpu, X amount for sound, X amount for the OS".
And then it allocates a certain threashold and says "okay this much I'm keeping free".
Then it says "these functions of the OS aren't used often, I'll leave them out".
Then it says "okay so I've got extra ram room, I'm going to fill them up with Apps".
Why does it work this way?
It based on Linux, RAM is shared dynamically.
What does this mean?
A bloated kernel and OS will use more RAM for itself.
Why does it leave free ram?
In case it needs to execute a function that's not used often or is memory intensive (eg Browser).
Why does it store Apps?
So that its readily available. They just pop open. Or resume from last state.
...okay, so what does this mean about my Free RAM "issues" with Jelly Bean?
It means that you are uneducated. It means Jelly Bean, or the specific setup you have either is more bloated than your previous setup OR it has a low "free ram allocation" setting. Solution? There is no problem, though you can trim down the ram allocation and kill off some memory things (apps, hidden background tasks) you can increase the amount of Free RAM, but its more likely to slow down the system. Remember, Jelly Bean builds are still Alpha/Beta stage, so they can/do have memory leaks.
Another point I should mention:
OS RAM use increased a lot from 1.6 -> 2.1
OS RAM use increased from 2.1 -> 2.2
OS RAM use increased a lot from 2.2 -> 2.3
OS RAM use increased a lot from 2.3 -> 4.0
< I haven't checked JB, but I'm willing to bet its increased from ICS, even if slightly >
This is Android, not Windows. Its behaves differently and has different symptoms. A quick Google search could've answered your questions.
Click to expand...
Click to collapse
Thanks for the lecture here :thumbup: I see now, I never get to know linux base very well. Just starting to get myself familiar with it.
I've used a few types of JB rom before and I discovered that its using double the ram from ICS making my phone lags and does funny things ut shouldn't. Ahaks
Than I noticed that JB was released to phones such as S3 and such, phones that has double the ram size to compare with note. Its when I started to wonder...
Sent from my GT-N7000 using xda app-developers app

Categories

Resources