Related
Hypothesis:
The memory for this device is contiguous with memory holes. This holes are for DMA for front/back camera, video decoding/encoding, etc. In 99.99% of time this is wasted memory.
Proposal:
Why not allocating all ram and dynamically allocating memory for DMA only when needed?
For example this could be like this:
1.The phone boots and the mm allocates all memory but lies the driver for camera that he could use a portion of ram for DMA
2.The system use normally all memory (maybe allocating last the reserved memory)
3.The user starts the camera
4.A hook in camera's driver instruct the mm that he needs the reserved memory
5.The MM frees a portion of ram(other than the one needed by the camera and equal with that) and moves everything from the reserved memory in that
6.The MM updates it's maps(virtual memory ↔ real memory)
7.The camera uses normally in DMA the reserved memory
8.The user closes the camera, the camera driver notifies the MM that he doesn't need memory anymore
9.The MM allocates normally the reserved memory
Pros: You'll have like 50% more ram in user space
Cons: Some lag when starting camera
I'm ready to start implementing this but I don't have lots of experience with the linux's mm and I don't really know if this is possible so I'm asking:
How crazy this idea is and it could be implemented? And if yes, how hard?
WOW! Your the first to suggest it. After everybody else here on forum, that is.
dupel said:
WOW! Your the first to suggest it. After everybody else here on forum, that is.
Click to expand...
Click to collapse
Yes, I know, the idea is not revolutionary or smth ) but I'm ready to try to implement it...
So please respond only if you can provide some useful information.
Not sure anyone really knows how easy it is to do for sure, but it has been mentioned a few times (but sounds like you have done it in further detail).
Personally, I've always believed that it's something which Samsung is working on, but maybe not. Could be awesome if you managed to make it work reliably.
Check out Hardcore's Speedmod kernel here in the development section.
His kernel gives you 341 RAM instead of the default 304. Might give you some ideas.
I know this isn't a bounty thread, but I would be willing to donate $20 if you could get this working. I wouldn't mind a slightly delay when launcher camera. I'd much rather have more free RAM.
andars05 said:
I know this isn't a bounty thread, but I would be willing to donate $20 if you could get this working. I wouldn't mind a slightly delay when launcher camera. I'd much rather have more free RAM.
Click to expand...
Click to collapse
I seriously think Samsung messed up a very good phone by allotting ONLY 512 MB ram. With 16/8 GB at their disposal, they could have easily allotted at least 1 gb
ragin said:
I seriously think Samsung messed up a very good phone by allotting ONLY 512 MB ram. With 16/8 GB at their disposal, they could have easily allotted at least 1 gb
Click to expand...
Click to collapse
+1 here!
I have the 16GB version so I wish Sammy gave this version at least 2GB RAM and 1 GB ROM
android.francis said:
+1 here!
I have the 16GB version so I wish Sammy gave this version at least 2GB RAM and 1 GB ROM
Click to expand...
Click to collapse
Can any developer DO THIS?
Seems simple. I think you need hack the pit file.
hi . . .
I dont want to be rude, but seeing these comments I couldn't stop myself -
Dudes, if you dont know what you are talking about STFU!!!
Seriously?? Allocate more to RAM from 16/8 GB??????? And edit the PIT file for this???? I am assuming that you all would've used computers, are you allocating more to RAM from the free space in your Hard Disk?? What you are suggesting is the same!!!
Please think for a moment before you post stuff.
And to the original query regarding how hard this would be - it would be pretty hard. You will have to touch upon everything that uses and reserves RAM. And this would also include modifying firmware of individual components on the phone. And if there are parts in this for which Samsung has not released source code, it would be very difficult. Not to say that - you could end up damaging the phone.
Good thoughts - but it would need a lot of work to get going.
Cheerios!!
Actually, using a swap partition on flash isn't that bad an idea, they are low latency. It would be pretty slow compared to physical ram though
Sent from my GT-I9000 using XDA App
coooolboyz said:
hi . . .
I dont want to be rude, but seeing these comments I couldn't stop myself -
Dudes, if you dont know what you are talking about STFU!!!
Seriously?? Allocate more to RAM from 16/8 GB??????? And edit the PIT file for this???? I am assuming that you all would've used computers, are you allocating more to RAM from the free space in your Hard Disk?? What you are suggesting is the same!!!
Please think for a moment before you post stuff.
And to the original query regarding how hard this would be - it would be pretty hard. You will have to touch upon everything that uses and reserves RAM. And this would also include modifying firmware of individual components on the phone. And if there are parts in this for which Samsung has not released source code, it would be very difficult. Not to say that - you could end up damaging the phone.
Good thoughts - but it would need a lot of work to get going.
Cheerios!!
Click to expand...
Click to collapse
My response: VIRTUAL RAM. And yes, I think before I post. My response was more of wishful thinking. So as an added response: ANALYZE and comprehend BEFORE you react. And I orginally was not suppose to reply but similar to you, I JUST COULDN'T STOP MYSELF
Now as for the topic of more RAM, I said before to check out Hardcore's SPEEDMOD KERNEL. It is fully functional and your RAM goes from 304MB to 341MB. Yes, it is hard but Hardcore already did it.
i have started my own and read every topic about why we could not see all the ram as user available (329 instead of 512) .. first i compared galaxy s with tab but it turned out tab has 640 Mb of real memory in total.. but i also have seen it was possible to add more memory about 40 Mb to the user available ram .. and i also learned there is also a part which is not used and called "blackhole" approximitely another 40 Mb..
so i believe it is possible to make some adjustments to improve the weakest (according to me) part of our galaxy s.. would some devs please mind trying this for us and share it?
We don't need the RAM (yet)
There are a lot of developers who try to get more out of our SGS's. For instance Juwe/ GingerReal increases the RAM to around 340MB.
Appearently Google thinks we don't need the full potential RAM and that's why they made it with a default of 300-330MB. Still still most developers agree on XDA that we should be able to acces the other 160MB because it doesn't do anything.
Until then we'll just have to wait.
even 340 Mb instead of 329 makes a difference .. i cant think what would happen with 380 or 400 or maybe even more..
because as far as i understood from what i have read; 128 memory is reserved for some drivers and capturing video is taking most of it.. i am taking a video maybe once in 2 monts.. but i am using my widgets, apps, playing my games everyday.. so if was asked to choose i would love to have that memory reserved for video taking..
edit:typo
First of all, the amount of RAM is NOT related to the ROM....
The kernel makes the difference...
In general the max amount of RAM in Gingerbread is 340MB, cuz if we go over the phone will become unstable and we'll break some functions like 720p recording....
In Froyo we used to reach max of 350MB without issues
just curiosity;
galaxy s2 and galaxy s has the same rams with different amounts.. what would happen if we soldered the 1gb ram to galaxy s? would it recognize it without any software tuning? or would we just kill the phone completely? or would still see 329 ?
simone201 said:
First of all, the amount of RAM is NOT related to the ROM....
The kernel makes the difference...
In general the max amount of RAM in Gingerbread is 340MB, cuz if we go over the phone will become unstable and we'll break some functions like 720p recording....
In Froyo we used to reach max of 350MB without issues
Click to expand...
Click to collapse
so is it possible to disable video recording completely and having lots of more Mb?
_delice_doluca_ said:
just curiosity;
galaxy s2 and galaxy s has the same rams with different amounts.. what would happen if we soldered the 1gb ram to galaxy s? would it recognize it without any software tuning? or would we just kill the phone completely? or would still see 329 ?
Click to expand...
Click to collapse
Do you want to instert 1GB ram into our SGS? I dunno sincerely what will happen.....
_delice_doluca_ said:
so is it possible to disable video recording completely and having lots of more Mb?
Click to expand...
Click to collapse
Probably yes, i am not a kernel expert, i am only a rom cooker/recognised developer, so my knowledge on kernels is very basic....
Maybe you'd better directly ask to a kernel dev like hardcore, nikademus, chainfire....
simone201 said:
Do you want to instert 1GB ram into our SGS? I dunno sincerely what will happen.....
Click to expand...
Click to collapse
i would really want that but i am sure its not as easy as soldering the gps antenna.. i have read about a HTC device getting a memory upgrade to 128Mb from 64 in xda forum.. so technically there is no impossible but i wonder what else need to be done after soldering the ram? software adjustments (kernel maybe?), or any more hardware changes ?
simone201 said:
Probably yes, i am not a kernel expert, i am only a rom cooker/recognised developer, so my knowledge on kernels is very basic....
Maybe you'd better directly ask to a kernel dev like hardcore, nikademus, chainfire....
Click to expand...
Click to collapse
thanks for tip, i will ask them..
i am really feeling bad about this ram issue.. every web page is showing nexus, galaxy s, galaxy tab have 512 Mb of ram.. but the memory dedicated for users is far less than the other 2 phones in galaxy s ... so it bothers me.. is there anyone who returns their phones to samsung and gets the money back?
first i believed somehow it was possible to use most of the ram with some software adjustement but then i realised even quadrant shows the total amount of ram memory is only 384 mb (and there is a part which is not used at all) ..
Is there any way to unlock htc rhodium's RAM from 288 to 512 ? As I found that this device has ( 288 MiB , 188.21MiB accessible ) RAM capacity. Look here:
http://pdadb.net/index.php?m=pdacomparer&id1=1751&id2=1931
lol, no. You can't just shove in more RAM, it's not a computer. Not made to be expandable...
then how about this??? see the spec.
http://www.howardforums.com/showthr...ith-AWS-3G-1700-2100-175-Today-Only-CanadaGSM
ciling said:
then how about this??? see the spec.
http://www.howardforums.com/showthr...ith-AWS-3G-1700-2100-175-Today-Only-CanadaGSM
Click to expand...
Click to collapse
A lie? I can say my TP2 has 1gb of RAM, doesn't mean it's true.
Edit - click on their specs link below. It's a misprint.
http://www.canadagsm.ca/HTC/HTC-Touch-Pro-2/
how about this? is it the possible way to unlock the hidden ram?
http://forum.xda-developers.com/showthread.php?t=667674
ciling said:
how about this? is it the possible way to unlock the hidden ram?
http://forum.xda-developers.com/showthread.php?t=667674
Click to expand...
Click to collapse
Do you even read what you're posting?
mweirauch said:
The assumptions made in the first thread are quite adventurous.
The Topaz only has 288MB RAM. Nothing more, nothing less.
That is 32MB of SMI memory soldered into the SoC (the MSM720xA) which is likely of fast SRAM nature. Then 2x128MB (external) EBI memory of slower SDRAM nature. On newer Topaz (as we've seen in the linux-msm kernel adventures) there can also be just 1x256MB EBI memory bank.
The 32MB bank is used entirely by the system and parts of the upper megabyte range of the first 128MB EBI memory as well. (Radio firmware, framebuffer memory, ...) The second bank is - as known until now - unused by the system and is available as RAM entirely.
Regarding memory setup: Every OEM is supposed to provide an OEMAddressTable definition for ARM based devices which is then used to initialize the processors MMU. This address table provides mappings between WinCEs virtual address range and the physical (memory) addresses. It might be possible to tweak that table when cooking the rom, but it's also very likely that malfunctions can appear by doing so. Really not worth the effort as the engineers have likely tuned it to the best already and you could gain perhaps - if possible at all - just some MB.
Let's be happy that we have the amount of memory that we have.
Click to expand...
Click to collapse
I read, but still hope for miracle from anyone...
Unless someone magically finds a radio that uses less memory and allows for more "free ram" (lay man terms and take the 2.22.27.08 radio for HTC Dream/Sapphire as an example which gained 14mb for system use), there really isn't much you can do other than remapping kernel memory banks available for camera/graphics/etc..
mweirauch explained phone memory pretty well in my opinion, and there are threads like this in almost every device section
e334 said:
there are threads like this in almost every device section
Click to expand...
Click to collapse
Everyone wants a magical placebo that will make their phones run 10,000x faster...
I guess it's human nature. Oh well.
So this is pretty crazy and weird but I killed all the apps running in the background and it says I'm using up 2.07gb of Ram how is that possible?
gator9422 said:
So this is pretty crazy and weird but I killed all the apps running in the background and it says I'm using up 2.07gb of Ram how is that possible?
Click to expand...
Click to collapse
Why does it matter? There is a ton of memory in this phone, and the OS manages it very, very well. You don't need spare memory. This isn't Windows, you won't run out of memory. It stores what it thinks it needs in RAM and keeps it there for quick access. It uses all the memory all the time (or at least it should). One of the things that prevents lag is to have the stuff loaded and ready at a moments notice.
Its a question of how the OS runs, not how much memory its taking. I would prefer if they hid that stat all together, then people would stop fixating on it, and loading efficiency killing memory manager apps.
Much like running defrag on a modern hard drive (they are supposed to be fragmented, they work better and faster that way) Android is supposed to run 90-95% used memory.. ALL THE TIME. Its the way its designed, and it works better that way.
One of the biggest misconceptions on all of XDA is about used RAM in a phone. People are always saying "OMG, there is only 500mb of unused RAM on my phone, it's going to slow down to a crawl!".
Just to be clear and hopefully people will understand it....unused RAM is wasted RAM. It does NOT have anything to do with slowing your phone down or anything like that. If there is 1gb of free RAM on your Note 4, that's totally fine.
Android manages RAM very well, don't stress. That's actually way more than it needs. You can only have 200mb of RAM free and your phone would still run fine. It's the way it's supposed to work. We have more than enough RAM in this phone.
I just hope this misconception will finally go away. I see at least a few RAM threads in every device forum.
It doesn't matter to me it's just the fact that I don't have any apps open and TouchWiz itself uses up 2gb of Ram to me that's a lot js
gator9422 said:
It doesn't matter to me it's just the fact that I don't have any apps open and TouchWiz itself uses up 2gb of Ram to me that's a lot js
Click to expand...
Click to collapse
It truly is a misconception. Android, windows, nix, any OS, for that matter. You would want too see your RAM being utilized. I would prefer to have my RAM used than not used at all because any unused RAM is a wasted RAM. This is also same with CPU. Unutilized cores are wasted cores. When writing software, one of the best practices is to learn how to use the memory to its full potential. You would want necessary stuff in RAM because using them when needed is faster if they are already loaded in memory than reinitializing the modules again and again every time for use. As far as memory location, RAM still provides the fastest. This is why in many companies that used gigabytes of data in their databases, a common practice in databadse engine technology is that they would actually load entire gigabytes of frequently accessed tables in memory for extremely fast access.
In short, don't worry
Thank you for the replies like they say you learn something new everyday. I appreciate the input
I'm more curious to know how the system manages to use more RAM every year with every new device released. Are there really that many more new features every year where they gobble up RAM?
gator9422 said:
Thank you for the replies like they say you learn something new everyday. I appreciate the input
Click to expand...
Click to collapse
http://searchstorage.techtarget.com/definition/cache-memory
Techweed said:
I'm more curious to know how the system manages to use more RAM every year with every new device released. Are there really that many more new features every year where they gobble up RAM?
Click to expand...
Click to collapse
My first computer had 512 mb RAM and it was fine at the time. Of course, with newer releases, they develop more features. With more features, more modules are created to support those features. Hence, more RAM usage.
^Wow, I think my first PC might have had 512 kb of RAM.
fbauto1 said:
My first computer had 512 mb RAM and it was fine at the time. Of course, with newer releases, they develop more features. With more features, more modules are created to support those features. Hence, more RAM usage.
Click to expand...
Click to collapse
That's true but with Kit Kat we were supposed to get a leaner running OS so that it would run on even old devices with minimum RAM. And I don't see how Touchwiz by itself could add 1 GB of RAM usage between the Note 2 and Note 4.
I would disagree on wanting all the ram to be being used... On previous rooted phones I have had (GS2, GS3, GSA4) getting rid of bloatware/useless apps eating up my ram made it much more responsive and fluid when opening new programs while significantly increasing battery life. Seems people just spew the bull**** marketing lines of Google across the internet and expect people to take it as truth. User experience is what is important, and getting rid of the garbage on any android version will make it faster. Not a difficult concept to understand.
rcracer_tx said:
I would disagree on wanting all the ram to be being used... On previous rooted phones I have had (GS2, GS3, GSA4) getting rid of bloatware/useless apps eating up my ram made it much more responsive and fluid when opening new programs while significantly increasing battery life. Seems people just spew the bull**** marketing lines of Google across the internet and expect people to take it as truth. User experience is what is important, and getting rid of the garbage on any android version will make it faster. Not a difficult concept to understand.
Click to expand...
Click to collapse
There is no bull**** here. Attend college and find out.
It is proven practice to use RAM
My source:
Myself with 15+ years as a software engineer
^^^This man speaks the truth. In my final year of my degree in software development and RAM utilization is common practice. User experience is different for everyone and what you "feel" is faster may or may not be an improvement.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
I think the goal of debloating should be to reduce the use of cpu by unwanted applications and reducing the amount of RAM taken up by them so that other applications may be cached instead. Whenever I debloat I start with watching applications that load and try to trim of the ones I know I don't need at all. I then move onto greenifying applications that run or cache themselves that I'll rarely use. Never in this process do I try to maximize free memory since doing so means applications that are not cached will take longer to launch. Im not sure if this is the right philosophy but it seems effective to me.
fbauto1 said:
There is no bull**** here. Attend college and find out.
It is proven practice to use RAM
My source:
Myself with 15+ years as a software engineer
Click to expand...
Click to collapse
I already have two degrees from a major big 12 university. And do a good amount of IT work for the business I work at. If you think that having your ram eaten up by programs you never use is good practice, maybe you need to re-evaluate the school you got your education. Using your logic our computers should be faster when they are full of **** running in the background... That's asinine. Full AND EFFICIENT utilization of ram is proven practice, not filling up ram full of bloatware.
muzzy996 said:
I think the goal of debloating should be to reduce the use of cpu by unwanted applications and reducing the amount of RAM taken up by them so that other applications may be cached instead. Whenever I debloat I start with watching applications that load and try to trim of the ones I know I don't need at all. I then move onto greenifying applications that run or cache themselves that I'll rarely use. Never in this process do I try to maximize free memory since doing so means applications that are not cached will take longer to launch. Im not sure if this is the right philosophy but it seems effective to me.
Click to expand...
Click to collapse
Well said, I agree. I guess I didn't make the distinction of when freeing up ram being eaten up by crap that will never be opened, What I mean is that cached memory being freed up is then able to be used by apps that I actually use. If over 2gb out of 2.92gb is being used all the time, (with the vast majority being eaten up by bloatware and the rest just being the base OS/UI) then that is not efficient utilization of ram. If you have to kill cached programs constantly and then load the new program you begin using, its going to take longer than having that program already having everything cached. In most times this is only milliseconds difference, but the fluidity of the transition is important to many as it is a significant factor in user experience. Who wants a phone that lags whenever a user input is made?
rcracer_tx said:
Well said, I agree. I guess I didn't make the distinction of when freeing up ram being eaten up by crap that will never be opened, What I mean is that cached memory being freed up is then able to be used by apps that I actually use. If over 2gb out of 2.92gb is being used all the time, (with the vast majority being eaten up by bloatware and the rest just being the base OS/UI) then that is not efficient utilization of ram. If you have to kill cached programs constantly and then load the new program you begin using, its going to take longer than having that program already having everything cached. In most times this is only milliseconds difference, but the fluidity of the transition is important to many as it is a significant factor in user experience. Who wants a phone that lags whenever a user input is made?
Click to expand...
Click to collapse
It is interesting that the vast majority of 2GB of your RAM is being using by bloatware. Between the Touchwiz function for turning off unneeded apps and Android's algorithms for determining what should be kept in memory, I find that "bloatware" apps (i.e., app I don't use) are practically non-existent in RAM...at least for me. That said, even if you still have 0.92 GB free, Android is not likely to decide it needs to kill an existing process to accommodate another program.
rcracer_tx said:
I already have two degrees from a major big 12 university. And do a good amount of IT work for the business I work at. If you think that having your ram eaten up by programs you never use is good practice, maybe you need to re-evaluate the school you got your education. Using your logic our computers should be faster when they are full of **** running in the background... That's asinine. Full AND EFFICIENT utilization of ram is proven practice, not filling up ram full of bloatware.
Well said, I agree. I guess I didn't make the distinction of when freeing up ram being eaten up by crap that will never be opened, What I mean is that cached memory being freed up is then able to be used by apps that I actually use. If over 2gb out of 2.92gb is being used all the time, (with the vast majority being eaten up by bloatware and the rest just being the base OS/UI) then that is not efficient utilization of ram. If you have to kill cached programs constantly and then load the new program you begin using, its going to take longer than having that program already having everything cached. In most times this is only milliseconds difference, but the fluidity of the transition is important to many as it is a significant factor in user experience. Who wants a phone that lags whenever a user input is made?
Click to expand...
Click to collapse
You are comparing RAM utilization to bloatware?
Where did you get your degrees, eBay?
fbauto1 said:
You are comparing RAM utilization to bloatware?
Where did you get your degrees, eBay?
Click to expand...
Click to collapse
No... he's not. Read it again. His point is that programs he doesn't need utilizing ram is bad.
We're playing a game of semantics here. He is working the angle that the original posts saying 'using ram is good' isn't true if it is crap that is using it.
Silly discussion at this point as both sides are correct based on the parameters of their view point.
Sent from my SAMSUNG-SM-N910A
Is that normal? How much free RAM do you guys have?
doesn't look like it, but mine is the same. I believe it is the lollipop memory leak issue...so as usual we just have to wait it out
Sucks that just as we are finally seeing 3 Gig of RAM we end up in the same situation as when we had 2Gig ?
I have not upgraded to to 2015 Flagship Standard yet but ...
I was hoping to START at the beginning of Boot Up with about
1.7 -2 GIGs of free RAM for Tasking etc.
I think " upgrading" to Lollipop on many Devices could create more problems than it solves - right ?
And the supposed Wifi Calling and VoLTE are not going to work
because they are Carrier Specific Software which must come directly from your Service Provider.
Free RAM is UNUSED/WASTED RAM! Understand? The more software/applications that are pushed into RAM the better because it is available to do whatever it needs to do without having to go and search for it and place into RAM! If and when you need more RAM for something new, say like opening another application...then Android will move out of RAM whatever is not being used and replace it with the new software. If your phone had 10GB of RAM it would still look nearly full. This is a GOOD thing. It's all still available for use when needed. Remember that RAM is always the fastest part of your phone. Of course the more RAM you have the more applications you can have open at any one time without any lag/stutter. But for now 3GB of RAM is quite good for a cell phone on Android.
XxKINGxX2580 said:
Is that normal? How much free RAM do you guys have?
Click to expand...
Click to collapse
Is that a built-in app showing you that?
DanRyb said:
Is that a built-in app showing you that?
Click to expand...
Click to collapse
Yes. it's called Smart Manager.
XxKINGxX2580 said:
Yes. it's called Smart Manager.
Click to expand...
Click to collapse
I just found it a few hours ago but thanks for replying LOL. This is my first Samsung that I'm using TouchWiz in years haha.
jaseman said:
Free RAM is UNUSED/WASTED RAM! Understand? The more software/applications that are pushed into RAM the better because it is available to do whatever it needs to do without having to go and search for it and place into RAM! If and when you need more RAM for something new, say like opening another application...then Android will move out of RAM whatever is not being used and replace it with the new software. If your phone had 10GB of RAM it would still look nearly full. This is a GOOD thing. It's all still available for use when needed. Remember that RAM is always the fastest part of your phone. Of course the more RAM you have the more applications you can have open at any one time without any lag/stutter. But for now 3GB of RAM is quite good for a cell phone on Android.
Click to expand...
Click to collapse
This right here, folks.
jaseman said:
Free RAM is UNUSED/WASTED RAM! Understand? The more software/applications that are pushed into RAM the better because it is available to do whatever it needs to do without having to go and search for it and place into RAM! If and when you need more RAM for something new, say like opening another application...then Android will move out of RAM whatever is not being used and replace it with the new software. If your phone had 10GB of RAM it would still look nearly full. This is a GOOD thing. It's all still available for use when needed. Remember that RAM is always the fastest part of your phone. Of course the more RAM you have the more applications you can have open at any one time without any lag/stutter. But for now 3GB of RAM is quite good for a cell phone on Android.
Click to expand...
Click to collapse
Come on... I have Galaxy S4 now (going for S6 today). The S4 comes with 1.8GB usable memory but when it reaches arount 1.5 GB it starts lagging, and by lagging I mean a lot! The fact is that when the device has less RAM it gets laggy and it works better when it has more free memory.
Anyway the higher memory usage is probably of how Lollipop works - it preloads the entire app in the RAM instead of loading it from the flash. It is meant to speed up loading but it takes more memory and I can argue for the effect.
once there are some custom roms, this "issue" will be addressed.
until then, you just have to deal with it