Related
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
.milFox said:
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
Click to expand...
Click to collapse
While I think having snapshot, replication, 100% consistency, and dedup capability would be the coolest thing on a phone, I think the ZIL would burn up the sd quicker and the resource utilization would eat battery and memory for the transactional caches to make it practical
.milFox said:
In general:
The problem with app2SD, in general, is slow SD card speeds.
Solution:
Hybrid storage pools, using the inbuilt applicaiton directory as the cache and the microSD directory as the main storage.
blogs.sun.com/ahl/entry/shadow_of_hsp explains some of the conceptual stuff
Issues:
ZFS is only available via FUSE
...
Thoughts?
Click to expand...
Click to collapse
My only thought is: "why?". I have every app I want installed and still have 102MB available. Given just how much more memory this has than the G1's of yore, I don't really see much of a reason for AppstoSD, especially since Google is releasing their own implementation *soon*.
I was already down to 29 Meg on my internal memory.
I'll be happy when Google implements a2sd. I can't see it being any different than what a2sd us doing though.
Just make sure you have a class 6 card.
Down to fairly minimal memory as well, here.
as to 'why' over conventional a2sd ... the in-built memory is faster than even a class 6 card. A hybrid zpool will allow the faster memory to cache the slower memory (normally, a hybrid zpool combines a SSD with a hard drive pool).
Ah, didn't realize people were having problems with it. Even so, Google has announced that they're working on it themselves and since it will be an actual part of the Android OS, rather than something hacked on, I imagine it'll be a better implementation that whatever we can do. I'll be waiting for that up and coming android release.
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Click to expand...
Click to collapse
I disagree, I only have 50 apps in total but have used 107Mb of my 196Mb used.
I lost 33Mb just flashing a theme.
Does anyone know if TA utility will work on the Nexus to move all the Caches?
Which memory are we talking about, primary or storage memory? If memory serves me correctly, the current os can only 256MB of primary memory but that will be increased to the full 512 in a later OTA update. I thought I saw some thread flying around here about that.
Amdathlonuk said:
I disagree, I only have 50 apps in total but have used 107Mb of my 196Mb used.
I lost 33Mb just flashing a theme.
Does anyone know if TA utility will work on the Nexus to move all the Caches?
Click to expand...
Click to collapse
You almost proved his point. 33MB is a ****ty size for a theme - get a better Themerto follow. Hell, most themes for Windows aren't that big.
-bZj
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
Click to expand...
Click to collapse
How on earth can you possibly make this judgment? Have you ever hear of cache? What about app data? Not to tout my own app (see sig), but the reason I created it was because my myTouch, with all of its storage, would run very low the regular basis. Besides, I like to download apps, both free and paid. Why should I be limited? Personally, I never even came close to filling up my 500MB ext partition on my myTouch but could easily have 50-100MB of cache in just a few days. I think having a GB of internal would suffice. It would allow me to comfortably add as many apps as I please and at the same time, not think about cache and data on the daily basis. $575 and I'm still going to have to hack a2sd on to this. I hate that. I'd much rather use internal storage.
Personally, I'm all for it. If nothing else, it would be one hell of a proof of concept and would likely be useful especially to those who like to run their devices lean and fast. There are too many nice things to say about ZFS, so I'll just say this: it's only a matter of time and what better time than now?
But I don't think it would happen, for the same reason ZFS hasn't been ported to linux, incompatible licenses.
http://zfs-fuse.net/
Can we get the ball rolling on this?
dont worry boys
A king nexus build is coming VERY soon with OPTIONAL a2sd and kingnexus kernel #1
SOON!
kingklick said:
dont worry boys
A king nexus build is coming VERY soon with OPTIONAL a2sd and kingnexus kernel #1
SOON!
Click to expand...
Click to collapse
So what's the Kingnexus kernel have?
cyanogen said:
So what's the Kingnexus kernel have?
Click to expand...
Click to collapse
+1 .... and how does it relate to ZFS (y on earth) and apps2sd?
~enom~
lmao you pissed of cyanogen ! xD
miketaylor00 said:
People who are running out of memory have way too many apps installed.
Anyway, I think you will find it very difficult to use the MTD block for this purpose.
Click to expand...
Click to collapse
Ever hear of games? Seriously, making a statement like this is just plain ridiculous. Homerun Battle 3D is over 30MB in and of itself. Yes, believe it or not, people actually use their nearly $600 3.7" screen for something other than reading email, of which I do plenty. So yes, I hacked apps2sd onto my Cyan ROM and it runs beautifully. I can't even tell the difference between this and internal it's so smooth. By the time Google releases a viable apps2sd the N1 will be yesterday's news. Internal storage and capacitive buttons = fail on the N1. Otherwise, kick ass device.
I never touched the kernal on alpha7 just added a s.d>placeholder in system int.d folder got apps2sd and the rest was set. Did not know kernal was part.
Hope the kernal is good.
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.
I'm currently running the devil kernel on my phone, using the new devil app to control settings but I really don't know a couple settings though. First what I'd zram and is it better than swap? And what's the best value to set the zram at? I have it on 150mb.
Also what's better zram or swap?
Dude look @ the op
Sent from my SGH-T959 using Tapatalk 2
No info about what it is in the op U_U
well, based on my reading...(Basically meaning take this with a grain of salt because I may not perfectly re-present the information, but this is how I've come to understand it lol )
zram basically compresses unused apps within the system RAM. This allows the system to swap less needed processes to the zram partition for faster access at a later time, instead of killing them. This does take up some of your ram though, so I imagine that the value you are setting is determining exactly what percentage of your ram that the zram partition is allotted.
Swap instead uses a small portion of the SDcard like RAM. The phone will attempt to keep as much within the ram as possible until fill, and then begin using the swap partition on the SDcard. At that point, the phone will begin moving inactive blocks of memory to the SD, freeing up RAM for active processes. If one of the pages on the SD needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the SD ('swapped').
Swap files don't restrict available RAM but writing to the sdcard impacts the speed of opening apps.
Now, which is better? No idea ^^ Lol
Holly crap I'm enabling swap lol. Do I need to repartition my SD card for swap?
I wouldn't enable swap, you don't need it, zram us nifty but also not need. Your system can handle memory just fine without you. Just let it to its thing and you will be fine.
Sent from my Galaxy Nexus using Tapatalk 2
I agree completely. My former device had a hack that we came up with that would force app2sd on a 2.1 build. This was great at the time but it cause some serious lag. We then enabled the swap to help with the memory issues. It worked for awhile but then all these apps started to come out that were, not to sound funny, memory hogs. This device only had 128mb of user RAM, so it was a constant struggle to get it working. Gotta remember that this was pre-GB times, so Froyo was the ICS of that time.
Here is more to read from this devices section about how swap works. The thread was revived on Post #9 and my explaination is Post#16.
Moral of the story is that I agree with Eco, let the phone work for you and not you against it. There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Woodrube said:
I agree completely. My former device had a hack that we came up with that would force app2sd on a 2.1 build. This was great at the time but it cause some serious lag. We then enabled the swap to help with the memory issues. It worked for awhile but then all these apps started to come out that were, not to sound funny, memory hogs. This device only had 128mb of user RAM, so it was a constant struggle to get it working. Gotta remember that this was pre-GB times, so Froyo was the ICS of that time.
Here is more to read from this devices section about how swap works. The thread was revived on Post #9 and my explaination is Post#16.
Moral of the story is that I agree with Eco, let the phone work for you and not you against it. There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Click to expand...
Click to collapse
Exactly, Android is designed for low Memory systems. It can handle out of Memory situations on its own, and will kill unneeded apps as is necessary to free ram for running apps. Don't worry about how much "free" ram you have because it doesn't matter. You want more free ram learn to set the ram usage settings to be more aggressive at killing idle apps. It'll and up using more battery, but if free ram is what you want then that's how to do it.
Sent from my Galaxy Nexus using Tapatalk 2
Woody said:
I agree completely. My former device had a hack that we came up with that would force app2sd on a 2.1 build. This was great at the time but it cause some serious lag. We then enabled the swap to help with the memory issues. It worked for awhile but then all these apps started to come out that were, not to sound funny, memory hogs. This device only had 128mb of user RAM, so it was a constant struggle to get it working. Gotta remember that this was pre-GB times, so Froyo was the ICS of that time.
Here is more to read from this devices section about how swap works. The thread was revived on Post #9 and my explaination is Post#16.
Moral of the story is that I agree with Eco, let the phone work for you and not you against it. There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Click to expand...
Click to collapse
Good old g1 and mytouch days
No signature for you!
Woody said:
There are few memory issues with the Vibrant. Is it running 2gb of RAM? No but do you really need something like that on a phone?
Click to expand...
Click to collapse
Actually, yes. There are certain apps, like Facebook, Whatsapp, Skype and probably more, that have their background services running even if you close the app. Those services are for sending notification, but they are slowing down this device very much (Even if only the Facebook service is running). So I do feel the device does not handle memory so good. And I can't blame it, since it has a limited memory, but I do wish I had more RAM.
Don't enable zram or swap unless you have the EU bug or like your shizz lag like a mo'fo'. If your phone is playing nicely, then disable both. Allow Purging of Assets also.Set it to two processes in Dev Section.
Sent from a Beaner
Like the SIG D'fresh!
Sent from my SCH-I535 using xda premium
Dougfresh said:
... Set it to two processes in Dev Section.
Sent from a Beaner
Click to expand...
Click to collapse
By this do you mean the "Background Process Limits"?
Sent from my SGH-T959 using xda app-developers app
scottPilgrim said:
hey devil, got a question for you...
any particular reason why you removed zRAM from your kernel? i was wondering if you could elaborate a little bit on why it isn't necessary on this device.
Thanks man
Click to expand...
Click to collapse
Xenoism said:
zram basically compresses unused apps within the system RAM. This allows the system to swap less needed processes to the zram partition for faster access at a later time, instead of killing them. This does take up some of your ram though, so I imagine that the value you are setting is determining exactly what percentage of your ram that the zram partition is allotted.
Click to expand...
Click to collapse
Not really needed on our device that have 2gb of ram memory.
Have ever been in a situation where you have been out of free ram? Neither have I.
Sent from my GT-N7100 using Tapatalk 2
Our devices don't have 2gb ram memory. They have 512mb ram memory
Sent from my SGH-T959 using xda app-developers app
cannondaleV2000 said:
Our devices don't have 2gb ram memory. They have 512mb ram memory
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
1+
Folks,
I need to know weather or not is it possible to increase the current RAM for the S3. I have a international version of the S3 in which the ROM has a limitation to 779MB. I hear some devices in US and Korea have a 1GB RAM. So if the device is the same is the RAM limited on the build or the hardware? And is it possible to increase the ram with a customer ROM?
mateenf said:
Folks,
I need to know weather or not is it possible to increase the current RAM for the S3. I have a international version of the S3 in which the ROM has a limitation to 779MB. I hear some devices in US and Korea have a 1GB RAM. So if the device is the same is the RAM limited on the build or the hardware? And is it possible to increase the ram with a customer ROM?
Click to expand...
Click to collapse
The international version has 1GB of RAM, I think the reason it shows 779MB is because the rest of the RAM is reserved as video memory. Don't quote me on that though.
P.S. The US and Korean versions have 2GB of RAM.
you cant increase it further 779 is the max you will get. us and international variants are different
The reason I asked is. I face alot of performance issues on the SGS3. My Memory always stays at 455 to 600MB usage. I dont have much applications installed .. Only basis ones that I need. Any ideas on optimizing the memory issue?
mateenf said:
The reason I asked is. I face alot of performance issues on the SGS3. My Memory always stays at 455 to 600MB usage. I dont have much applications installed .. Only basis ones that I need. Any ideas on optimizing the memory issue?
Click to expand...
Click to collapse
Are you running the stock rom at this moment or do you have a different launcher?
Its the default rom and unrooted. And also the defualt launcher in S3
Sent from my GT-I9300 using xda app-developers app
You would be better off waiting for the Jelly Bean upgrade in a few weeks .
jje
I don't think RAM is the problem for your performance. My S3 is also running between 450 and 600 and I don't have any performance issues..
There are some tweaks you can try under Settings -> Development like animation scale and background process limit.
When do you have the performance problems?
Do u really think JB will increase perfomance? And I honestly dont think that OTA will be relased anytime in this quater! Plus i prefeer the ripple effect in ICS would samsung keep that in JB too?
Sent from my GT-I9300 using xda app-developers app
klm67637 said:
I don't think RAM is the problem for your performance. My S3 is also running between 450 and 600 and I don't have any performance issues..
There are some tweaks you can try under Settings -> Development like animation scale and background process limit.
When do you have the performance problems?
Click to expand...
Click to collapse
I see battery issues at times, also when I clear RAM to free up some memory the home screen goes blank and then appears, I have formatted my phone also, but even using a plain S3 and trying to clear RAM my screen still goes blank. Is this a known issue within S3 when clearing RAM?
bala_gamer said:
you cant increase it further 779 is the max you will get. us and international variants are different
Click to expand...
Click to collapse
Is this a hardware limitation or the build?
mateenf said:
I see battery issues at times, also when I clear RAM to free up some memory the home screen goes blank and then appears, I have formatted my phone also, but even using a plain S3 and trying to clear RAM my screen still goes blank. Is this a known issue within S3 when clearing RAM?
Click to expand...
Click to collapse
mateenf said:
Is this a hardware limitation or the build?
Click to expand...
Click to collapse
When you clear your RAM..all the cache which was generated gets removed hence when you go to your homescreen again..that data has to be loaded again ..and hence the delay...dont try to force your phone..Android has a very good memory management ..it will do it for you..clearing RAM all the time will just make your launcher and other most used apps slow to open...
Yes it is a hardware limitation..we have only 1 GB of inbuilt RAM..of which 221 MB is used by system and the rest is left for your apps...
mateenf said:
I see battery issues at times, also when I clear RAM to free up some memory the home screen goes blank and then appears, I have formatted my phone also, but even using a plain S3 and trying to clear RAM my screen still goes blank. Is this a known issue within S3 when clearing RAM?
Click to expand...
Click to collapse
So you have some battery issues.. Try JuiceDefender to increase your battery life or System Tuner to check the apps that are running in the background...
JuiceDefender:
https://play.google.com/store/apps/...xLDEsImNvbS5sYXRlZHJvaWQuanVpY2VkZWZlbmRlciJd
System Tuner:
https://play.google.com/store/apps/...ch_result#?t=W251bGwsMSwxLDEsImNjYzcxLnBtdyJd
klm67637 said:
I don't think RAM is the problem for your performance. My S3 is also running between 450 and 600 and I don't have any performance issues..
There are some tweaks you can try under Settings -> Development like animation scale and background process limit.
When do you have the performance problems?
Click to expand...
Click to collapse
Tweaks? You shouldn't have to make tweaks to the follow up to the sgs2 with super duper quad core!
Fact is you probably do.. The sgs3 is a fail. There are undeniable performance issues. It is on par with the ZTE Blade.
mwatson said:
Tweaks? You shouldn't have to make tweaks to the follow up to the sgs2 with super duper quad core!
Fact is you probably do.. The sgs3 is a fail. There are undeniable performance issues. It is on par with the ZTE Blade.
Click to expand...
Click to collapse
Agreed, I am really not satisfied with the performance of a quad core processor!! A quad code with a 2100 mah battery is decent but not upto mark what you expect the phone to give an output.
I was better satisfied with my galaxy note with a 2500 mAH battery which ran 3 days using EDGE and 2 days if I'm using HSPDA!!
zoot1 said:
When you clear your RAM..all the cache which was generated gets removed hence when you go to your homescreen again..that data has to be loaded again ..and hence the delay...dont try to force your phone..Android has a very good memory management ..it will do it for you..clearing RAM all the time will just make your launcher and other most used apps slow to open...
Yes it is a hardware limitation..we have only 1 GB of inbuilt RAM..of which 221 MB is used by system and the rest is left for your apps...
Click to expand...
Click to collapse
But it should be possible to use a full 1GB RAM with custom ROM's. Like ive seen a MIUI ROM that allows a full 1Gb usable on the SGS3
http://www.youtube.com/watch?v=T5oSnIgZ_4g
mateenf said:
But it should be possible to use a full 1GB RAM with custom ROM's. Like ive seen a MIUI ROM that allows a full 1Gb usable on the SGS3
http://www.youtube.com/watch?v=T5oSnIgZ_4g
Click to expand...
Click to collapse
Dear Sir, the miui rom shows you the complete 1 GB but the extra 221 mb is not available for your apps..if you have noticed even after a fresh intall the available Ram will hover somewhere around 600-700 MB and not 800-900 MB..
it is just how it is displayed and not used..
hope it will clarify your doubts..
I had huge memory leak issues. My ram used to fall even below 50 MB even after removing all bloat. I finally found the solution by moving to "Foxhund Rom". I have applied his min free ram tweaks. Now My ram never falls below 200 MB which is good enough to run heavy process.
I dont know howto increase RAM storage but there is a way to increase data storage.
Look here
LMFAO some of the comments in this thread are seriously pathetic! Performance issues with this phone? Making it comparable to ZTE Blade? Iphone users and trolls in here much?!?
This phone, bone dry stock is blazing fast and incredibly smooth and with the latest stock latest firmware the home screen redraw is so smooth it doesn't even look like it's redrawn.
With custom roms that keep 200mb clear in RAM all the time, there is no multi tasking because the phone is constantly closing apps to keep 200mb free. It's just to keep people happy that they can see free ram! If it's never used, it's useless..
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