Related
I have installed RAM Booster and ZD Box(task killer) to help free up RAM, however i feel that the RAM usage on my x10 is still too high.
On average the free RAM on my phone is between 40MB -60MB, is that normal?
My question is how else can i free RAM on my phone? will installing apps to SD Card help? Also my internal memory widget is reading "414MB used out of 465MB" thats sound too high. my phone feels laggy and ive even stopped using live wallpapers, sumtimes the phone would even reboot on its own but hasnt done so in a while.
if u install too much apps without using app2sd, its normal to have that amount of ram.. i recommend u to use link2sd, u can manually select apps to move to sd. bt make sure that dont move any widget apps to sdcard or else it will stop functioning and appearing in ur widget list
I use Advanced Task Killer, from the market.
That being said, Android naturally will kill processes and apps. It waits for a certain amount of time, or until the resources are needed elsewhere. You shouldn't have to wory about how much free ram you have available... Unlike Windows, Android will manage it all on it's own!
khakhi said:
I have installed RAM Booster and ZD Box(task killer) to help free up RAM, however i feel that the RAM usage on my x10 is still too high.
On average the free RAM on my phone is between 40MB -60MB, is that normal?
My question is how else can i free RAM on my phone? will installing apps to SD Card help? Also my internal memory widget is reading "414MB used out of 465MB" thats sound too high. my phone feels laggy and ive even stopped using live wallpapers, sumtimes the phone would even reboot on its own but hasnt done so in a while.
Click to expand...
Click to collapse
Use auto memory manager free from market
Requires root and when set to aggressive free ram great
Doesn't eat battery as it isnt a task killer
Sent from my X10i using XDA App
to OP i wish i am a mod so i can move your post to Q&A thread.. geezzzzz
Eddie_Brock said:
I use Advanced Task Killer, from the market.
That being said, Android naturally will kill processes and apps. It waits for a certain amount of time, or until the resources are needed elsewhere. You shouldn't have to wory about how much free ram you have available... Unlike Windows, Android will manage it all on it's own!
Click to expand...
Click to collapse
then y does my phone feel laggy if u say android will manage processes on its own? im going to try "link2sd" now and see how it goes.
Free RAM is wasted RAM, why don't people get that?
theskeptic said:
Free RAM is wasted RAM, why don't people get that?
Click to expand...
Click to collapse
not if it's causing his phone to reboot and have problems because he is using it all...
xcxa23 said:
if u install too much apps without using app2sd, its normal to have that amount of ram.. i recommend u to use link2sd, u can manually select apps to move to sd. bt make sure that dont move any widget apps to sdcard or else it will stop functioning and appearing in ur widget list
Click to expand...
Click to collapse
link2sd is telling me i need to partition my sd fisrt and im not sure how to, im going to try apps2ds
First i don't this is a place to post such question, there is a section called Q&A.
Second, i recommend using AutoKiller Memory Optimizer, it's super amazing and very essential app for me. I get usually more than 100 MB free RAM most of the time, and it's easy customizable, after your read the help section.
Give it a try
it wouldnt be a lack of memory causing a phone to reboot but the app w memory leaks causing the phone to reboot. the apps youre killing werent designed for you to kill them unexpectedly. they were designed to run any necessary cleanup routines on exit. if the app youre killing doesnt have an option to exit, then you should replace it w one that does or ask the author to provide an exit/close for the app to free itself from the list of running processes.
you're introducing dirty unintended states for the apps and the os by killing them unexpectedly. you will have immediate gains in performance and will gain unexpected problems when those same apps go to run later. lost widgets, widget data, duplicate widgets, or maybe even break an app that wasnt designed to open from a dirty state.
keep an eye on the tasks, but leave them alone if you can.
Sent from my X10i using Tapatalk
silv3rfox said:
First i don't this is a place to post such question, there is a section called Q&A.
Second, i recommend using AutoKiller Memory Optimizer, it's super amazing and very essential app for me. I get usually more than 100 MB free RAM most of the time, and it's easy customizable, after your read the help section.
Give it a try
Click to expand...
Click to collapse
Thanx guys will try it...
to op, i think u better try the autokiller 1st. because the link2sd and app2sd need to make partition.
1st make a fat32
2nd make a ext2
size of partition 2 put less than 1gb, i assuming u having a 8gb class 2 sdcard
the rest of it goes to fat32
ps : this require u to format ur sdcard. so make sure u backup it up in ur pc
khakhi said:
link2sd is telling me i need to partition my sd fisrt and im not sure how to, im going to try apps2ds
Click to expand...
Click to collapse
Apps2sd needs partition as well... try a partitioning program and make a main fat32 partition and then a second one ext2 partition (i suggest 1gig max should be more than enough)
You don't want to free up ram. It messes with your phone. Your suppose to use ram
Sent from my X10i using XDA App
Get rid of the task killer and get AutoKiller Memory Management. I went from ~35mb free to ~135mb by changing the last 3 settings to 150, 200, 250 and never need to kill anything
Sent from my X10i using XDA Premium App
i use automatic task killer and it works pretty good for me...
Hi, i recommend the app "Taskiller Full" from AxDroid LLC ( i dont know if the free version is the same ) when i kill apps get a 150-200 free ram
do NOT use task killers. all you will succeed in doing is to use MORE battery. Andoid (which is linux based) is designed to have very little free memory. The way android handles application and memory use is it keeps frequently launched apps in memory so they launch quicker. if a task comes along that requires resources android will simply ditch the reserved memory (that is reserved in case you launch a particular app that is in memory) and will allow it to be utilised for the new app. as has been said 1000's of times before, free ram is wasted ram!
all a task killer will do is to fight against the native android instruction set, each time android attempts to launch a process into ram the task killer will kill it, and each time this happens it will chew a bit more battery life.
having a lack of ram is not necessarily the reason your handset is lagging.....the perceived lack of ram is only because it is earmarked for potential use.
my advise to you? just leave it be, maybe reboot your handset a bit more frequently, and remove some of the apps that you have installed that are fighting against android!
good luck!
theskeptic said:
Free RAM is wasted RAM, why don't people get that?
Click to expand...
Click to collapse
+++ exactly, let your phone do the thinking! (bump)
Sent from my X10i using XDA Premium App
After googling and searching alot, i didnt find my answer
so hope someone can help me here, and this will help others too.
so install apps on SD Card or Internal memory ?
The internal phone memory is generally of a lesser amount than the amount of the memory you'd have on a SD card. You cannot really change the amount of internal memory you have on your phone but you can always get a new SD card with a larger storage capacity.
So when you have apps that need a lot of space it is better to have them installed on the SD card.
will installing more apps on internal memory make the phone run slower ???
I don't think it will make the phone run slower, but you'll have lesser storage space for your other data which is stored in the internal storage like your contacts etc.
i have an HTC Sensation XE running on Darkforest ROM, this is my RAM (pic) how can i increase the free memory, thats the max i get around 180MB free
View attachment 1034360
Can I know why you wish to free up the RAM? In most cases you really don't need to because the OS manages that quite efficiently. It will free up the RAM and make room for the running applications whenever it needs to.
cuz in some apps after opening them for a while and try to close this app the phone restarts, so i read that its cuz of low RAM
please correct me if am mistaken
180 mb is a lot of RAM for a single application to use. And as I said, the OS, is pretty good at managing it. Although I cannot exactly tell you why your phone might be restarting when you close some apps, I don't really think it would be cause of the low RAM.
I checked my phone and it had about the same amount of RAM occupied as yours(i.e. 2 thirds of the total capacity). Then i started a game called Fruit Ninja which uses 3d graphics, which should need a lot of RAM. Then i pressed home and checked the RAM usage again. Even then the RAM usage did not go up by much.
You should try to verify this on your phone too. Check the amount of RAM thats being used. Then start the application thats causing the problem. Press the home button and check the RAM usage again.
An app will probably run quicker from internal mem because flash storage is much slower, but youre'e limited by space constraints.
Sent from my MB526 using XDA
Well it might load into the RAM quicker. But I don't really think there is much of a difference in speed while its running. Unless there are a lot of loading and writing operations.
Pay attention to one thing: internal storage and ram are not the same thing.
Ram is commonly allocated on a high speed journaled partition and it is 1000 times or more faster than both the internal emmc or the external SD (that'd why a swap partition is not as fast as real ram).
Just for the I/O parallelism, an app installed on the external sd could very likely run faster than one that resides in the internal emmc. Anyway, it also depends on the class of the external sd, though the class counts only when writing sequential data, while reading could even be faster when using a lower class SD.
lucaoldb said:
Pay attention to one thing: internal storage and ram are not the same thing.
Ram is commonly allocated on a high speed journaled partition and it is 1000 times or more faster than both the internal emmc or the external SD (that'd why a swap partition is not as fast as real ram).
Just for the I/O parallelism, an app installed on the external sd could very likely run faster than one that resides in the internal emmc. Anyway, it also depends on the class of the external sd, though the class counts only when writing sequential data, while reading could even be faster when using a lower class SD.
Click to expand...
Click to collapse
Doesn't an application get loaded into the RAM first when its started? So would its execution speed still depend on the sd/internal memory?
I thought that would come into the picture only when theres some kind of read/write thats happening to the sd/internal memory...
Well, if it is true that any app run inside the dalvik vm and such vm is able to run simultaneously multiple apps in its sandbox, I suppose that any app could need to access its installation files and its stored data while running.... I am not sure, anyway, it is just what I believe it could be.
To be true, my supposition mostly derives from what I've experienced with chrooted linux, which run faster when the .img file is stored on the external sd.
Anyway, if it should be as you say, the app's speed would be totally independent from the support where it was installed.
lucaoldb said:
Well, if it is true that any app run inside the dalvik vm and such vm is able to run simultaneously multiple apps in its sandbox, I suppose that any app could need to access its installation files and its stored data while running.... I am not sure, anyway, it is just what I believe it could be.
Click to expand...
Click to collapse
That is what I exactly meant. Although it differs from case to case, an application typically loads all the stored data it needs at the start. And then throughout the execution of this application, loading/saving of data is generally rare.
Of course this is a very generalized statement and such things are handled differently by different applications depending on how they were implemented and what they are intended to do.
Consider for example a game. The game would load all the textures, images, music it would need for a particular level. Then throughout the entire period of the level the game wouldn't need to load any data. It is only when some different support data would be needed by the game, or if the player's state is to be saved there would be a read/write operation. At such a time only would there be a need to access the sd/internal memory. So it really doesn't make the difference of where the game is installed very noticable.
Now on the other hand if you have an application say an Image viewer application which loads an image from the the sd/internal memory every time the "next" button is pressed. Then, maybe you'd have a noticable difference based on where the image is being loaded from. But even typical image viewers implement some sort of image caching to reduce such excessive loading.
Widgets
I had a problem where apps that used a widget option did, not give that feature anymore when the app is moved to the SD card...
Im using pacman 18 on my neo v (JB rom)
Never really had a ram problem untill lately, when i started using viber, whatsapp, swype...
Now phone is struggling, there are no cached processes and almost no memory free.
By default zram is using 18% of my memory.
I dont exactly know what is zram, googling didnt help.
If i understand correctly, there are 2 scenarios:
1) It compresses data that would be in memory anyway, so you gain more ram, at the cost of having to compress/decompress evey time.
2) Apps that would normally be killed, are kept compressed inside memory, for faster access, at the cost of 'live' memory.
Could someone please clarify this for me?
well i dont know many things either.
I just think of this as that:
there is a swap/page file in ram that compresses useless/unused apps in ram.
Something like NTFS compress ability.
if you are using windows you have probably noticed that in the properties menu it says compress file to save disk space.
Well it just compresses it in ram and when you will need it it will be decompressed.
That way you will have more ram but maybe lags when swiching to apps.
I dont know anything about pacman rom so i can tell you about your problem.
try deleting zram (it will probably be a script in init.d)
I know it compresses data in phone's ram.
My question is, where does that data come from?
1) If that data would be in memory anyway, and they are just compressed, it gives you more memory, at the cost of performance
2) If they were outside of memory, and zram puts the in memory compressed, you lose ram, but you gain performance.
Let me also rephrase:
If i disable zram, that data that it compressed, would still be in memory uncompressed?
Or they will not be kept in memory any more?
Sorry, my English isnt helping on this one...
gordito_gr said:
I know it compresses data in phone's ram.
My question is, where does that data come from?
1) If that data would be in memory anyway, and they are just compressed, it gives you more memory, at the cost of performance
2) If they were outside of memory, and zram puts the in memory compressed, you lose ram, but you gain performance.
Let me also rephrase:
If i disable zram, that data that it compressed, would still be in memory uncompressed?
Or they will not be kept in memory any more?
Sorry, my English isnt helping on this one...
Click to expand...
Click to collapse
From Wiki
"zRam is an available feature for certain distributions of Linux, that was previously called "compcache". It increases performance by avoiding paging on disk and instead uses a compressed block device in RAM in which paging takes place until it is necessary to use the swap space on the hard disk drive. Since using RAM is faster than using disks, zRam allows Linux to make more use of RAM when swapping/paging is required, especially on older computers with less RAM installed.
Even though the cost of RAM hardware is relatively low this feature still offers advantages for netbooks and other lower-powered latops, virtualization and in the case of embedded devices, especially those that use flash memories that have a limited lifespan, dependent on write-use and thus wear out quickly when used as a swap device."
So the data are still in RAM but compressed...yes if you disable Zram they will be still there but they will use more ram! You gain more free ram when u use Zram but your CPU load is higher so perfomarnce is almost the same..
Konstantinosj77 said:
So the data are still in RAM but compressed...yes if you disable Zram they will be still there but they will use more ram! You gain more free ram when u use Zram but your CPU load is higher so perfomarnce is almost the same..
Click to expand...
Click to collapse
Still not clear.
On linux, after ram is depleted, data is coming from page file (hard disk)
How does zram work?
Does it pre-occupy that space in ram?
Or when ram is depleted, zram is automatically enabled and it starts compressing data???
gordito_gr said:
Still not clear.
On linux, after ram is depleted, data is coming from page file (hard disk)
How does zram work?
Does it pre-occupy that space in ram?
Or when ram is depleted, zram is automatically enabled and it starts compressing data???
Click to expand...
Click to collapse
Read again the part from the wiki..it says that zram uses "a compressed block device in RAM" so yes it pre-occupy some ram like a swap file! Also read this http://forum.xda-developers.com/showthread.php?t=2023568
Hi people!
i've found this
http://forum.xda-developers.com/showthread.php?t=2145133
tested it on my device and work fine with CM 10.1
waithing for the official release
How did you manage to make it work?.. i can update it with the cwm and neither the manual way.. with terminal it says not writable (but it is!)
uc370 said:
How did you manage to make it work?.. i can update it with the cwm and neither the manual way.. with terminal it says not writable (but it is!)
Click to expand...
Click to collapse
Try to change permissions using root explorer or es file manager
Sent from my XT910 using xda app-developers app
Permision were changed.. terminal still says only red file
uc370 said:
Permision were changed.. terminal still says only red file
Click to expand...
Click to collapse
I don't know why terminal see only read but if you do cat /proc/swaps you will see how swaps are working
Sent from my Folio 100 using xda app-developers app
And what should it look like?.. q tendria q salir.. aprox 51000 50000 -1
vince686 said:
Hi people!
i've found this
http://forum.xda-developers.com/showthread.php?t=2145133
tested it on my device and work fine with CM 10.1
waithing for the official release
Click to expand...
Click to collapse
I've been trying this patch (manually, not the complete script), but I have found this actually slows down the folio. There is a reason why flash-based devices don't have a swap. When writing large blocks to swap, the system will stutter heavily. The slow flash disk of the folio will not help in this. My test shows it is actually slowing down quite a bit.
Even with the low RAM of the folio, it is still faster to just start/restart an app than to swap it away in a swapfile (resulting in 1secs of stutter) and then getting it back anyway from disk.
ZRAM is something similar. Tough here I can understand some improved use cases, but:
- you take away precious RAM
- then you swap out programs and compress them (uses a lot of CPU)
- if you swap the program in again, you need to decompress. Granted, the decompress might be a little faster than restarting the app.
- because of the lower useable memory, programs do have an higher chance than before to be compressed (vs killed without ZRAM), so decompression (with ZRAM) statistically will happen more than restarting (without ZRAM), making the gains of ZRAM point 3 less.
- I don't think this works correctly with huge processes (e.g. browser), and will just see that less RAM is available, and will not swap out parts because the whole memory region is still in use (best case, it will continuously swap in & out parts, making it again slower)
I'm not completely trowing out ZRAM, as it is still beneficial with some workload combinations (I think a large collection of small apps is the most optimal case)
Hey guys .. today i increased my RAM using some methods on the internet but RAM Expander Didn't work it says : swapon sdcard/swapfile.swp invalid argument ... so my problem is i have used . Sawpit Ram Expander and succeed but when i check my ram .. it still the same no changes & nothing happened please help me ASAP​
Well you can add physical ram to a phone, you can flash a kernel or bootloader that reallocates some ram, but this is device specific and often takes some very intelligent programmers to make this happen.
The other way is to use virtual ram in the form of a swap partition, this will use sdcard or internal data or whatever partition you make work, function as ram, but it is slower than real ram and depending on how you use your device may make it slower altogether. I believe this is the method of increasing ram that you did, the easiest way to see if it worked is to open a terminal emulator and type
free
The final way is with compcache or zram, both squash ram and has a similar caveat to using swap as it may make things worse.
A few Google or xda searches should explain this a bit more than I have
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thanks for your help
demkantor gonna try zram soon​
demkantor said:
Well you can add physical ram to a phone, you can flash a kernel or bootloader that reallocates some ram, but this is device specific and often takes some very intelligent programmers to make this happen.
The other way is to use virtual ram in the form of a swap partition, this will use sdcard or internal data or whatever partition you make work, function as ram, but it is slower than real ram and depending on how you use your device may make it slower altogether. I believe this is the method of increasing ram that you did, the easiest way to see if it worked is to open a terminal emulator and type
free
The final way is with compcache or zram, both squash ram and has a similar caveat to using swap as it may make things worse.
A few Google or xda searches should explain this a bit more than I have
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Rooted !