I am running a custom rom with a kernal (devil) that allows for Swap
I have been getting posts that both say swap is great and swap is essentially pointless. My google research comes to similar results so I put it to you my fellow fassy users. Should I use swap? Why or why not?
swap is much slower than the true ram.
Related
Developers please help. It seems that our Nexus Ones are restricted to only 180 MB RAM as their is a bug in the kernel. Can anyone make or compile a RAMhack that can open up the extra 100-150 MB RAM. The below is an excerpt from another thread under the Nexus One - Nexus One forum here in XDA. Im wondering how much faster this thing will fly. It seems a MEMhack such as the one they used to free the 10MB for the dream might be the same approach. Apparently Google will patch this but there is no ETA on the next update.
A "memhack" kernel update in the next Nexus One OTA should give us an additional 100-150MB RAM. Who wants to try to compile a kernel that does this now?
reserved for space
flak0 said:
Developers please help. It seems that our Nexus Ones are restricted to only 180 MB RAM as their is a bug in the kernel. Can anyone make or compile a RAMhack that can open up the extra 100-150 MB RAM. The below is an excerpt from another thread under the Nexus One - Nexus One forum here in XDA. Im wondering how much faster this thing will fly. It seems a MEMhack such as the one they used to free the 10MB for the dream might be the same approach. Apparently Google will patch this but there is no ETA on the next update.
A "memhack" kernel update in the next Nexus One OTA should give us an additional 100-150MB RAM. Who wants to try to compile a kernel that does this now?
Click to expand...
Click to collapse
it's really only a matter of time on this ... once the 2.6.3x kernel is perfected for the mahimahi HW ... we'll get it. Think tank not really necessary ... as it's in the works.
~enom~
Ummmm. I thought that was the goal here:
http://forum.xda-developers.com/showthread.php?t=616383
Doubt we need the 2nd thread.
That is correct that is the goal however, until the .32 kernel is perfected is there a way to hack the current Kernel like it was done for the Dream to get the extra memory back. I am just making a suggestion. I know the only issue with the .32 kernel is the proximity sensor fails from what I have read. Can this be confirmed?
All sensors work fine with 2.6.32. Google put the sensor code in git a few days ago. I am having issues with the camera, but another person in the kernel thread said he got it working, but I can't confirm it yet.
As for the memory hack, I do not know how to do it, but the memory map and allocation are in <kernel dir>/arch/arm/mach-msm and the two files are line 959 in board-mahimahi.c and board-mahimahi.h has the memory map table breakdown.
Edit: I just got the camera working
Wont enabling that ram for program use affect the GPU(Like on the G1)?
~~Tito~~ said:
Wont enabling that ram for program use affect the GPU(Like on the G1)?
Click to expand...
Click to collapse
No, there is ram that isn't even allocated in the nexus unlike the G1. You would just move everything around and nothing would be adversely affected (in theory).
staulkor said:
No, there is ram that isn't even allocated in the nexus unlike the G1. You would just move everything around and nothing would be adversely affected (in theory).
Click to expand...
Click to collapse
Thats a bug google said would be fixed and more ram would be avail for the Nexus.
According to swetland, the only way is via the .32 kernel due to the problems caused by the 1:1 requirement. Otherwise it sounds like things go bad very quickly.
swetland said:
Roughly 220MB is available to userspace in the shipping build (ERD79).
Quite a lot of memory is dedicated to the radio firmware (41MB), dsp firmware (32MB), display surfaces (32MB), gpu (3MB), camera (8MB), a/v buffers (41MB), and dsp buffers. Much of this needs to be set aside for these specific tasks due to hardware requirements of very large physically contiguous buffers which can be difficult or impossible to obtain after boot once the physical memory space gets fragmented.
The big limitation though is that the Linux kernel needs to do a 1:1 physical:virtual map of general purpose memory used by the kernel and userspace (which excludes the special purpose stuff described above). This eats into the available kernel virtual address space, which is also needed for cross process shared memory used by the binder, etc. Run out of virtual memory and things get unhappy.
In 2.6.32, HIGHMEM support for ARM will allow us to avoid this requirement for a 1:1 mapping which will allow us to increase memory available to userspace without running the system out of virtual memory adddress space.
Click to expand...
Click to collapse
bofslime said:
According to swetland, the only way is via the .32 kernel due to the problems caused by the 1:1 requirement. Otherwise it sounds like things go bad very quickly.
Click to expand...
Click to collapse
Thanks for the details. I wasn't aware of what was causing the problem before reading this. This makes a lot of sense.
Hello people. I wanted to know is the compcache is more effective than swap file usage or not. And could we use them both and will it be more useful. Or anybody have better idea of it. Cause u know that our devices have small amount of Ram.
So has anyone tried swap on this device?
I was thinking that we might be able to increase ram operation if there was a swap partition.
I'm not exactly sure if it will work....
If anyone see's this thread and has a class 10 micro sd card and they want to try it please let me know how it affects the benchmarking results.
(I'd do it, but I have a crappy class 4)
Darin_Ram said:
So has anyone tried swap on this device?
I was thinking that we might be able to increase ram operation if there was a swap partition.
I'm not exactly sure if it will work....
If anyone see's this thread and has a class 10 micro sd card and they want to try it please let me know how it affects the benchmarking results.
(I'd do it, but I have a crappy class 4)
Click to expand...
Click to collapse
I tried using swap for awhile on my old HD2 which only had .5gb, but not here. The question I have to ask is why? In most of the current ROMs developers have already added scripts that kill dormant processes to free up real memory. Even when I've got a dozen apps open I've got plenty of RAM available. What kind of out of memory issues are you experiencing where you think swap would help?
Odysseus1962 said:
I tried using swap for awhile on my old HD2 which only had .5gb, but not here. The question I have to ask is why? In most of the current ROMs developers have already added scripts that kill dormant processes to free up real memory. Even when I've got a dozen apps open I've got plenty of RAM available. What kind of out of memory issues are you experiencing where you think swap would help?
Click to expand...
Click to collapse
Well it's not exactly a out of memory problem. I just wanted to see if the performance would be affected if a linux swap partition for ram would increase or decrease the ram operation.
I know we don't have the most high end device out there, but the specs are supposed to be better than an S2, yet it surpasses ours. It has a slower processor and less 3d graphics than the amaze and still it beats it.
Ram operation on the S2 according to Antutu: 705
Ram operation on the Amaze according to Antutu: 356
That's about half!!!!!
And I'm pretty sure if we found a way to increase the ram operation it'd help with all the other results.
I don't know why this is the case, but probably has more to do with the software running on the devices than the components. Sense is a lot of things most of which are good, but one thing for sure is it's s resource hog.
Odysseus1962 said:
I don't know why this is the case, but probably has more to do with the software running on the devices than the components. Sense is a lot of things most of which are good, but one thing for sure is it's s resource hog.
Click to expand...
Click to collapse
I believe my rom is senseless, cause I'm on the Xperia Z Ultra by shubham211995
Hello,
I'm using an app called RAM EXpander to increase swap in order to unlag my phone wich is running many many apps...
IM using an Xperia S and it doesnt have much ram, and this was the only solution to keep everything running and to not make lag in my phone..
So the question is, how safe can be the use of this kind of apps in relation of the flash memory usage (readings/writings)..
AFAIK it'll do some harm in the long term, but what long term means?? 2 years? 1 month and it'll kill my phone flash memory?? 10 years??
I've seen in XDA and all over the web, people that comment on how bad is using flash as a swap because of the writing limitations in flash memory, but still havent seen an actual case of a dead flash memory... LOL
thank you in advance
Anyone?
Is it still possible to increase the RAM size of the Poco F1? I have the 6gb/128gb variant and I want to have maybe 2 to 4gb more RAM. I read around that it can be done with a swap file on older phones but I already tried that and even added up to 6gb but it doesn't seem to get used. Is there a custom ROM or magisk zip that can be used for that? My phone currently runs on Corvus with NGK.
The reason why I want more RAM? Egg NS. My phone frequently runs out of RAM and the game force closes.
Thanks!
Oyee said:
Is it still possible to increase the RAM size of the Poco F1? I have the 6gb/128gb variant and I want to have maybe 2 to 4gb more RAM. I read around that it can be done with a swap file on older phones but I already tried that and even added up to 6gb but it doesn't seem to get used. Is there a custom ROM or magisk zip that can be used for that? My phone currently runs on Corvus with NGK.
The reason why I want more RAM? Egg NS. My phone frequently runs out of RAM and the game force closes.
Thanks!
Click to expand...
Click to collapse
What are these apps and games you use?
How do you fill the entire memory?
I switched to LineageOS + NGK because it's more stable. So far I only have DamonPS2 and Egg NS installed after flashing the ROM. Had no problems with DamonsPS2 even with stock ROM. Anyway, I said before the app in question is Egg NS, a switch emulator. The app needs 8gb RAM so the Poco F1 is short of 2gb that's why it force closes randomly. I get smoother framerates compared to stock but then I still run out of RAM.
Well, short of swapping the DRAM modules for bigger ones it would be impossible, and even then who knows if it would work?
Although now that you've posted this question, I'm left wondering if anyone has successfully done this… I know that Scotty from Strange Parts (and others) have swapped NANDs for bigger storage, but RAM I've never seen.
I think ram is included in the SOC, which means cpu, gpu, controllers, everything else will be also replaced if someone were to upgrade ram, basically changing the core of the phone.
I'm trying to make it work like this one. A really old post from 2012 so I doubt it'll still work for Android 10.
https://forum.xda-developers.com/showthread.php?t=1659231
Oyee said:
I'm trying to make it work like this one. A really old post from 2012 so I doubt it'll still work for Android 10.
https://forum.xda-developers.com/showthread.php?t=1659231
Click to expand...
Click to collapse
In that case why don't you try zRAM instead? Depending on the kernel your zRAM (or swap, for that matter) capabilities may differ, but give it a go!
IDK about other kernel utility apps, but EX Manager has the options.
Ok I'll give that one a try. Just tried Roehsoft RAM expander and it still works but the game runs really slow when it's already using the swap memory. At least it doesn't force close now. lol