Hey guys
I'm sure you all know that the milestone and droid are outdated. The processor is too slow and there isn't enough ram. Thankfully the processor is easily overclocked without increasing the voltage by that much but the ram is an issue. I know that on the droid you can use swap but that is no where near as fast as ram.
So basically I was hoping for an app that enables a "gaming mode". This could move the android system onto the swap space (becomes very laggy) leaving 256mb of ram which is surplus for all games.
I know swap can't be done on the milestone yet. But do you guys think its possible and has it been done before?
Charlie
Sent from my Milestone using XDA App
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
Dear all,
I am curious if I can purchase a larger RAM module and replace the one in my SGS resulting in more RAM space available to applications?
My SGS is running fast but I have a lot of applications installed which utilize RAM in background. As everyone know although SGS claim to have 512MB memory, the actual memory available for user application is around 3xx MB only. I am woundering if upgrade of physical RAM is feasible.
Thanks!
HKcow said:
Dear all,
I am curious if I can purchase a larger RAM module and replace the one in my SGS resulting in more RAM space available to applications?
My SGS is running fast but I have a lot of applications installed which utilize RAM in background. As everyone know although SGS claim to have 512MB memory, the actual memory available for user application is around 3xx MB only. I am woundering if upgrade of physical RAM is feasible.
Thanks!
Click to expand...
Click to collapse
I'd highly doubt that it would be possible. Maybe some high skilled person could make the swap (it probably wouldn't be easy to find one..), but no-one knows if it would have even theoretical chances to work. And yes SGS has 512mb of ram..but os and apps just take their part of it in any situation.
Sent from my GT-I9000 using xda premium
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
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.