hi guys,Does Quasar kernel support swap?and how to enable it?
i tried to enable it but failed
and i'm thinking about there's a lot of free space that i never used in /data and /system,so why don't we use those useless space to swap for more ram?
or we can use ZRAM?and how to use it?
we have 512 mb memory, for what you want swap?
actually the ram we can use only have less than 300mb
hmm partitionning SDC should do the job, isn't it ? do "ext" partitions have something to do with that ?
I think there's no reason to use swap, but dxdiag32's idea is not bad... internal memory is quicker than sd...
Regards.
Nah, it doesn't support it.
I did some tests with ZRAM and ZCache back in the LG P500 days and it didn't seem to help with anything so I usually disable Swap support now.
Anyway, you can always mount a tmpfs partition to some applications to boost their I/O operations if that's what you're looking for.
Huexxx said:
I think there's no reason to use swap, but dxdiag32's idea is not bad... internal memory is quicker than sd...
Click to expand...
Click to collapse
Depends on the microSD card's class. A class 10 is faster than internal memory.
In fact, it's a shame they dropped the yaffs2 filesystem as in non-sequential I/O operations it's the best one.
Class10 is faster? At least internal memory will be less energy hungry... won't be?
Huexxx said:
Class10 is faster? At least internal memory will be less energy hungry... won't be?
Click to expand...
Click to collapse
Yes, class 10 (>= 10 mb/s write speed) is faster than internal memory.
This is why moving app, data and dalvik to microSD when you have such microSD provides a good boost on I/O operations. There's many folks using the combo CM + S2E + MicroSD Class 10.
As for battery, it's a good question but I bet it should be the same. I/O stuff isn't heavy.
most of us now is using C4 sdcard,at least in China is .so i wanna give us some more performance.my free space in /data partition keep more than 800MB for a long time,and i think more ram can provide us more stable phone.
Beware that RAM works differently for Android devices.
Whereas free RAM in Windows is arguably better than occupied RAM, this is not so for Android. In Android, having RAM allocated is good which is also behind the reason of why we shouldn't use task killers. That being said, we don't really need more than 512 MB of RAM for a heapsize of 32 MB and proper OOM groupings and adj values! Even with an aggressive usage, it's unlikely you'll manage to trigger an OOM (out of memory) throughout your day.
Here's an oldie but goldie article regarding this:
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
ok got it , thanks knzo
knzo said:
we shouldn't use task killers.
Click to expand...
Click to collapse
I understand the theory but because of my own experience I do not agree in 100% with You. My previous smartphone was Samsung Spica ( not much RAM ). I used to use my favourite IGO for navigation. It was impossible to succesfully launch IGO if I have not used task killer before.
Without task killer IGO just started and vanished within seconds.
pabgar said:
I understand the theory but because of my own experience I do not agree in 100% with You. My previous smartphone was Samsung Spica ( not much RAM ). I used to use my favourite IGO for navigation. It was impossible to succesfully launch IGO if I have not used task killer before.
Without task killer IGO just started and vanished within seconds.
Click to expand...
Click to collapse
That's because IGO triggered an OOM event and the ROM you had instead of doing an intelligent swipe and killing applications based on certain heuristics, was killing the process responsible for the OOM instead (IGO). It's a flag in sysctl called: OOM kill allocating task.
So in that case, it was just a lousy ROM/kernel. Or perhaps in Spica (old kernel, old android version) there wasn't this setting and the phone always killed the application that made the phone run out of memory. This explains why it vanished after a bit.
Either way I stand correct, there's no need for task killers in a device with >= 256 MB of RAM or properly configured.
knzo said:
That's because IGO triggered an OOM event and the ROM you had instead of doing an intelligent swipe and killing applications based on certain heuristics, was killing the process responsible for the OOM instead (IGO). It's a flag in sysctl called: OOM kill allocating task.
So in that case, it was just a lousy ROM/kernel. Or perhaps in Spica (old kernel, old android version) there wasn't this setting and the phone always killed the application that made the phone run out of memory. This explains why it vanished after a bit.
Either way I stand correct, there's no need for task killers in a device with >= 256 MB of RAM or properly configured.
Click to expand...
Click to collapse
Agreed. I still have my old Galaxy Apollo, with 256 MB ram it goes perfectly as it should. In fact, on a careful observation i 've noticed that if we use taskkiller at autokill level at let's say 30 minutes autokill, it will technicall consume 4 CPU cycles in an hour for each app (two for killing, and two when applications like gmail/facebook etc. starts automatically again).. but without taskkiller they may have stay idle, and not used any CPU cycle at all for as many hours as phone is idle. And for battery purpose, it is the CPU cycle that drain, not the used memory !
in my opinion,we only need to kill the apps that use internet in background to save battery.such as Google Maps,once i used it,its services stay in background and after 3 hours i didn't use phone do anything,battery drain 3%,and if i kill it,no battery drain after all
Google Maps and DRM service process sometimes cause battery drains indeed.
knzo said:
Google Maps and DRM service process sometimes cause battery drains indeed.
Click to expand...
Click to collapse
i deleted DRM service,and seems it's no harm to system
Lol but do you know what is it function ?
Sent from my LG-P970 using xda premium
I've seen drm using a lot of CPU as well from time to time. What is it used for and how would you go about removing it?
dxdiag32 said:
i deleted DRM service,and seems it's no harm to system
Click to expand...
Click to collapse
Sent from my LG-P970 using XDA App
masterthor said:
I've seen drm using a lot of CPU as well from time to time. What is it used for and how would you go about removing it?
Sent from my LG-P970 using XDA App
Click to expand...
Click to collapse
You can use Titanium https://market.android.com/details?id=com.keramidas.TitaniumBackup
-Go to Backup/Restore tab
-Find by DRM Protected Content Storage
-Click and select Freeze
Now the app is Freeze and the system don't see more!
Related
Hi, I was wondering if I can use the 10 mb ram hack with my g1 with CM 6.0 RC2. I noticed most of the tutoriials are using 4.xx.xx so I wanted to ask before I do it. My phone is kind of slow even though it is overclocked at 576mhz and 64 mb class 6 memory swap. Thanks.
Ties0 said:
Hi, I was wondering if I can use the 10 mb ram hack with my g1 with CM 6.0 RC2. I noticed most of the tutoriials are using 4.xx.xx so I wanted to ask before I do it. My phone is kind of slow even though it is overclocked at 576mhz and 64 mb class 6 memory swap. Thanks.
Click to expand...
Click to collapse
There is no 10 mb hack and won't be. It is not possible with Froyo.
As indicated above there is no 10mb hack and there never will be.
I am currently using the latest nightly and it is super fast and stable. As fast as donut (no ****).
3D Gallery works perfectly and there have been a bunch of small cool features added to the nightly.
I highly recommend it.
Awesome work has been done by Cyanogen and Crew.
ok thanks for the reply guys. Is there any other way to make my rom faster? Thanks.
Ties0 said:
ok thanks for the reply guys. Is there any other way to make my rom faster? Thanks.
Click to expand...
Click to collapse
Of course reduce or remove swap,
android has it's own swap mechanism that causes little ram to actually be least recently used, thus if swap is enabled the phone will be constantly swapping it in/out!
In addition to reducing the life of the SD card its slow. I understand a very little bit of swap *may* allow some edge cases where a *little* more ram is needed or to offload something like launcher that may be configured to stay in ram to work faster.. however you can't forget the speed issue.
Try this enter console on your phone and run:
dd if=/dev/zero of=/sdcard/swapspeedtest bs=1048576 of=64
Note the time it takes, that is the time to write 64mb on a swap out operation.. if it seems too long to wait for a task its too much swap. 12mb is almost acceptable. I just stick to comp cache only. . Upped it from the default 12 to 15 MB since I had one or two tasks that just needed a tad more memory to play nice.
Also what is slow, returning to home? A particular app? I doubt its everything, usually its launcher and there are ways of locking it in home, upgrades to awd, and alternative launchers. These may help.
ezterry said:
Of course reduce or remove swap,
android has it's own swap mechanism that causes little ram to actually be least used, thus if swap is enabled the phone will be constantly swapping it in/out
In addition to reducing the life of the SD card its slow. I understand a very little bit of swap to allow some edge cases where a little more ram is needed or to offload something like launcher that may be configured to stay in ram.. however you can't forget the speed issue.
Try this enter console on your phone and run:
dd if=/dev/zero of=/sdcard/swapspeedtest bs=1048576 of=64
Note the time it takes, that is the time to write 64mb on a swap out operation.. if it seems too long to wait for a task its too much swap. 12mb is almost acceptable. I just stick to comp cache only. . Upped it from the default 12 to 15 MB since I had one or two tasks that just needed a tad more memory yo play nice.
Also what is slow, returning to home? A particular app? I doubt its everything, usually its launcher and there are ways of locking it in home, upgrades to awd, and alternative launchers. These may help.
Click to expand...
Click to collapse
Thanks for the detailed response! I will try lowering the swap partition, I always thought it would be fast because of the class 6 speeds. Does putting all my apps on SD make it slow as well? Also, returning to home is the main lag I'm talking about as it takes quite a while to see my apps. Thank you!
ezterry said:
Of course reduce or remove swap,
android has it's own swap mechanism that causes little ram to actually be least used, thus if swap is enabled the phone will be constantly swapping it in/out
In addition to reducing the life of the SD card its slow. I understand a very little bit of swap to allow some edge cases where a little more ram is needed or to offload something like launcher that may be configured to stay in ram.. however you can't forget the speed issue.
Try this enter console on your phone and run:
dd if=/dev/zero of=/sdcard/swapspeedtest bs=1048576 of=64
Note the time it takes, that is the time to write 64mb on a swap out operation.. if it seems too long to wait for a task its too much swap. 12mb is almost acceptable. I just stick to comp cache only. . Upped it from the default 12 to 15 MB since I had one or two tasks that just needed a tad more memory yo play nice.
Also what is slow, returning to home? A particular app? I doubt its everything, usually its launcher and there are ways of locking it in home, upgrades to awd, and alternative launchers. These may help.
Click to expand...
Click to collapse
I have about 3-5 apps that I would like to be running at one time? Should I be using CompCache or Swap? Currently I am on SuperD 1.9.3 WGK. I have been reluctant to run Froyo roms because they are so much more memory hungry in my experiences. My current rom runs pretty fast with a 96mb swap. If I were to fun a Froyo rom, what can I do to be able to run the 3-5 apps and retain speed?
Ties0 said:
Thanks for the detailed response! I will try lowering the swap partition, I always thought it would be fast because of the class 6 speeds. Does putting all my apps on SD make it slow as well? Also, returning to home is the main lag I'm talking about as it takes quite a while to see my apps. Thank you!
Click to expand...
Click to collapse
If you are using BOTH SWAP & have applications installed to the sdcard, then it will ****REALLY**** be slow.
With just applications on the sdcard, your speed should be fine.
Ties0 said:
Also, returning to home is the main lag I'm talking about as it takes quite a while to see my apps. Thank you!
Click to expand...
Click to collapse
This is a symptom of launcher being evicted from ram, try the stay in ram option in settings->adw launcher->system settings->system persistent in the more recent versions of adequate (I think included with rc2 if my memory serves me)
It may not be perfect as it will still get killed if a very large application is loaded.
Either you need a launcher that behaves as a good android application, and can quickly reload it's last state, even if it was not in ram when you requested it.. or launcher needs to be considered outside the usual android memory management and to be kept in ram.
These persistent processes are where you may depending on your usage of the phone find comp cache or swap in low amounts (32mb combined is probably the absolute max) may help as they will have allocated ram that is rarely used and not automatically freed as they are persistent..
ezterry said:
This is a symptom of launcher being evicted from ram, try the stay in ram option in settings->adw launcher->system settings->system persistent in the more recent versions of adequate (I think included with rc2 if my memory serves me)
It may not be perfect as it will still get killed if a very large application is loaded.
Either you need a launcher that behaves as a good android application, and can quickly reload it's last state, even if it was not in ram when you requested it.. or launcher needs to be considered outside the usual android memory management and to be kept in ram.
These persistent processes are where you may depending on your usage of the phone find comp cache or swap in low amounts (32mb combined is probably the absolute max) may help as they will have allocated ram that is rarely used and not automatically freed as they are persistent..
Click to expand...
Click to collapse
Thanks for the detailed response! I just changed the adw launcher and deleted my swap partition... It seems to be much slower when pressing home (icons are taking a while to load) so I might just use 32 mb for swap.
EDIT: question, what exactly does ext4 do? I know swap is like external ram, but what does ext4/ext3/etc exactly do? and how much should I put in? I tried googling but could not find the answer. Thanks!
Ties0 said:
EDIT: question, what exactly does ext4 do? I know swap is like external ram, but what does ext4/ext3/etc exactly do? and how much should I put in? I tried googling but could not find the answer. Thanks!
Click to expand...
Click to collapse
On CM6, nothing. On CM 4 & 5, it was used for Apps2Ext (formerly known as Apps2SD - before Google came out with their own flavor). However, CM6 does not have Apps2Ext. It has been indicated that it will be targeted for 6.1.
Hi again guys...
In Linux we have a SWAP partition for some time if RAM (Random Access Memory) will full OR for speed up applications by buffering in swap partition.
(Recommend Linux SWAP partition size: half of RAM)
so Android is Linux based and have kernel like Linux. Is it work to make a SWAP partition for SGS with swap file system?
You don't want that...
Android doesn't wipe RAM immediately anyway, so apps which are open and shutdown can be restarted again quickly (unless the RAM has been reused).
Also, apps on Android are designed to be shut down whenever free RAM runs out (its in the development guidelines that all applications should expect to be shut down at any time). Since most Android phones use high-speed NAND memory, when properly configured, apps load quicker too
The problem with swap is that it can lead to thrashing and loss of battery life. It's good for computers (because generally, you would rather lose performance and ensure you don't lose work), but on Android, applications should be killable at any time, and should have mechanisms to protect their work anyway.
It's probably possible to create a swap partition/file if you wish (try to swapon), but I foresee some potential side-effects, especially if you don't want to spend a lot of time managing memory manually.
i didn't think about battery life.
Thank you so muchhhhhhhhhh
I was actually exploring this option last night and stumbled that the kernel does allows swapon commands. I remembered trying it earlier on a stock rom but it was not available then.
Why I need the swap was because of the frequent shutdown of my launcher pro due to apps contenting for memory. The live wallpaper and heavy Widgets like pure messenger pro aren't helping much either, after much usage the device just slows down, lags and silently kills the background apps. The "minfree" settings were also tweaked but with much less desirable results was seen...
So I downloaded an app called "swapper2" from market and tested via 2 methods; Swap file and swap partition.
The performance of a swap file that sits in the NAND is not really that great. In fact it kinda lags me when memory is being swapped in and out of it. I think its the same problem with the i/o lag problems with any other rom
Then I tried a swap partition on my class 6 SD card. Although the lifespan of the card would be shortened and the battery life would be impacted, the performance is better compared to the earlier method.
In either method, the amont of apps that can be left opened at the foreground and background had increased and doesn't lag as more apps is being launched. Not bad for me but well, I guess it's all up to the user of the device at the end. Just my 2 cents...
I'll try the swap file method again over at the ext2 partition created by the lagfix and see how it goes next. Not sure if anyone interested though...
Sent from my GT-I9000 using XDA App
It seems that using the swap partition doesn't have the lag compared to using the swap file method.
It may be due to the I/O of multiple storage (parallelism ?) is better than a single storage or writing into the raw partition is better in terms of performance than a swap file.
I'm done with my findings, the device still have 60mb free and never lags, I'm sold.
Sent from my GT-I9000 using XDA App
Upgraded to froyo JPH last night and have noticed that autokiller doesn't work so well with it. When using autokiller with all the 2.1 fw's it did it's job and you could see which apps were the empty apps etc. However with froyo the empty apps don't show up and autokiller doesn't seem to be able to perform correctly, currently I have it set to aggressive but I can see my phone go to 70mb free. I have emailed the dev but no response as of yet, anyone else had this issue or know how to fix not being able to kill empty apps ? Cheers.
Sent from my GT-I9000 using XDA App
Daley87 said:
Upgraded to froyo JPH last night and have noticed that autokiller doesn't work so well with it. When using autokiller with all the 2.1 fw's it did it's job and you could see which apps were the empty apps etc. However with froyo the empty apps don't show up and autokiller doesn't seem to be able to perform correctly, currently I have it set to aggressive but I can see my phone go to 70mb free. I have emailed the dev but no response as of yet, anyone else had this issue or know how to fix not being able to kill empty apps ? Cheers.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Why you're using a autokiller app?
The phone got ram to be used. If theres no further ram available for apps android will clear it by itself.
I´m on JPH and there's 192 of 304 MB used.
There's 112 MB free ram!
because auto killer alters androids minfree settings unlike regular task managers that kill everything, also with a bit of use my phone is displaying just over 60mb free resulting in a slow phone.
Sent from my GT-I9000 using XDA App
i can't use my phone without autokiller...
jeanveupas said:
i can't use my phone without autokiller...
Click to expand...
Click to collapse
Maybe you should clean up your phone. I if u installed millions of apps its clear that your phone slows down.
Daley87 said:
because auto killer alters androids minfree settings unlike regular task managers that kill everything, also with a bit of use my phone is displaying just over 60mb free resulting in a slow phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Instead of Autokiller, use OCLF http://forum.xda-developers.com/showthread.php?t=784691
I hate to change the Android default settings for file system and minfree, however after applying the lagfix, absolutely no lag and my phone flies despite several days of excessive use with all possible apps.
If you don't need Lagfix, you could still use the apk for minfree settings and apply on boot.
60MB of free RAM should not cause you any slowness issues. RAM is there to be used, I would want Android to use the entire memory and be efficient in managing virtual memory rather than WASTING RAM by NOT utilizing it for open apps.
Prankey said:
Instead of Autokiller, use OCLF http://forum.xda-developers.com/showthread.php?t=784691
Click to expand...
Click to collapse
Both programs do exactly the same. OCLF even refers to Autokiller as in "using the same names and values for defaults".
I would want Android to use the entire memory and be efficient in managing virtual memory rather than WASTING RAM by NOT utilizing it for open apps.
Click to expand...
Click to collapse
With "strict" setting I always have enough ram and still dozens of reportedly running apps. The Android way of multitasking is working really good, it just needs some fine tuning with the Galaxy S. Somehow, the default settings cause too much cleaning up right when you start certain apps, this it feels laggy even though the RFS factor has been removed (e.g. with Voodoo).
gpnda said:
Maybe you should clean up your phone. I if u installed millions of apps its clear that your phone slows down.
Click to expand...
Click to collapse
I have installed millions of apps, and it is running blazingly fast (using Autokiller to "strict" and Voodoo on JM8). Why shouldn't I? What else is nearly 2GB of user apps space meant for? Why are there so many apps in the store?
Prankey said:
Instead of Autokiller, use OCLF http://forum.xda-developers.com/showthread.php?t=784691
If you don't need Lagfix, you could still use the apk for minfree settings and apply on boot.
60MB of free RAM should not cause you any slowness issues. RAM is there to be used, I would want Android to use the entire memory and be efficient in managing virtual memory rather than WASTING RAM by NOT utilizing it for open apps.
Click to expand...
Click to collapse
OCLF minfree settings, minfreemanager and autokiller all do the same thing - they change the same configuration file that controls Android's memory management tool.
I agree though, that the optimal amount of free RAM seems to be 60M-70M on our phones. The default configuration in the Samsung Froyo firmwares set it to about 40M-50M (the last 3 values in minfree are 40/44/48 by default).
And also, it is a misconception that "free" RAM in Linux is wasted. The free RAM is not unused, but is used by the OS to cache the disks, which is why the phone is faster with more free RAM. On our Samsungs this has a huge effect because RFS is slow and a big disk cache will help it a lot.
You can see this by doing:
# cat /proc/meminfo
cat /proc/meminfo
MemTotal: 311348 kB
MemFree: 16088 kB
Buffers: 12196 kB
Cached: 91344 kB
SwapCached: 0 kB
Active: 185192 kB
Inactive: 44792 kB
jeanveupas said:
i can't use my phone without autokiller...
Click to expand...
Click to collapse
5 big Widgets at Homescreen, 12 Apps opened (ICQ, Google Mail, Browser, MP3-Player, Touiteur, Titanium Backup, XDA, Market, ES File Explorer, YouTube and so on), 90mb free ram and the Phone is still running smooth.
Don´t know what you´re doing wrong.
Running JPH for 71 hours now without using autokiller and it has run great without much lag.
Mainly browsing internet, video, music, email and games without issue. And reply messages and calls.
Sent from my GT-I9000 using XDA App
PlanetJumble said:
Both programs do exactly the same. OCLF even refers to Autokiller as in "using the same names and values for defaults".
Click to expand...
Click to collapse
I agree, suggested as I felt "Autokiller" might not be working correctly in Froyo.
PlanetJumble said:
With "strict" setting I always have enough ram and still dozens of reportedly running apps. The Android way of multitasking is working really good, it just needs some fine tuning with the Galaxy S. Somehow, the default settings cause too much cleaning up right when you start certain apps, this it feels laggy even though the RFS factor has been removed (e.g. with Voodoo).
Click to expand...
Click to collapse
My experience was different. If I just use the OCLF 2.04 and do not tweak with file system and minfree settings, my phone is working perfectly no matter how many apps I load and how long I use (used alteast for 3 days without any lag issue)
PlanetJumble said:
I have installed millions of apps, and it is running blazingly fast (using Autokiller to "strict" and Voodoo on JM8). Why shouldn't I? What else is nearly 2GB of user apps space meant for? Why are there so many apps in the store?
Click to expand...
Click to collapse
I COMPLETELY agree. We are not talking of Windows 9x which could not manage memory well. We are talking of Linux which should work perfectly even when we have several apps running.
hardcore said:
OCLF minfree settings, minfreemanager and autokiller all do the same thing - they change the same configuration file that controls Android's memory management tool.
I agree though, that the optimal amount of free RAM seems to be 60M-70M on our phones. The default configuration in the Samsung Froyo firmwares set it to about 40M-50M (the last 3 values in minfree are 40/44/48 by default).
And also, it is a misconception that "free" RAM in Linux is wasted. The free RAM is not unused, but is used by the OS to cache the disks, which is why the phone is faster with more free RAM. On our Samsungs this has a huge effect because RFS is slow and a big disk cache will help it a lot.
You can see this by doing:
# cat /proc/meminfo
cat /proc/meminfo
MemTotal: 311348 kB
MemFree: 16088 kB
Buffers: 12196 kB
Cached: 91344 kB
SwapCached: 0 kB
Active: 185192 kB
Inactive: 44792 kB
Click to expand...
Click to collapse
I believe the cached portion shows as used memory. We may have to revisit this discussion. As whenever I use memory cleaners, I felt my system went worse if I keep more memory available (except for opening apps which uses the available memory instantaneously). So I doubt free memory (I am not talking of the default available memory on Android) can be used for cache when forcefully freed by these settings/apps.
Aery said:
5 big Widgets at Homescreen, 12 Apps opened (ICQ, Google Mail, Browser, MP3-Player, Touiteur, Titanium Backup, XDA, Market, ES File Explorer, YouTube and so on), 90mb free ram and the Phone is still running smooth.
Don´t know what you´re doing wrong.
Click to expand...
Click to collapse
xtrememorph said:
Running JPH for 71 hours now without using autokiller and it has run great without much lag.
Mainly browsing internet, video, music, email and games without issue. And reply messages and calls.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Completely agree, when I tweak with Minfree settings and the file system to "Deadline" it becomes more "jerky". Others might have different experience, however I strongly believe that while RFS definitely slows down write speeds, default minfree settings and the file system optimization should be optimum for "regular" use.
Every time I flash firmware, I try first without the lag fix, then with the lag fix, and finally, with autokiller, and every time autokiller has helped noticeably.
As things stand at the moment, its one app I wouldn't be without, lag fix or no lag fix.
Working well here. JPH firmware, autokiller set to strict, 91mb free. 3 days of uptime
Hi
Dunno if this is possible, but when I think of windows computers back in the days, it was possible to use som of the harddrive as allocated memory.
Is this possible with the o2x? 512mb seems to be a little low on 2.2.2. Guess it will be better on 2.3... but, in the meantime, is it possible from a rooted o2x to use my internal or external as allocated memory...
I got a sh*tload of apps installed, and is down to 75mb RAM available, and it is getting a bit laggish... I've installed Zeamlauncher, and frozen LG 2.2.2 UI, and other unnessacary apps. But I'm still low on memory
Short answer is no.
Longer answer is if you have 75MB free you don't need any more... that's heaps!
There's no point in having a lot of free ram, you only need as much as the next task wants so that Android doesn't need to swap out memory.
Available ram will not affect performance unless it's lower than ~20MB.
Use autokiller (free on market), it can adjust the android memory config settings.
Functional on LG 2x (root needed)
I just thinks the o2x gets laggier and laggier as days go by
at first it was real fast, but then as it got filles up with apps, its getting slower...
got some quite long hangtimes sometimes. espacially when installing a new app.
This was not the situation in the first couple of days. Had it for about 14 days now, and its not as optimal as in the beginning.
Guess I'll just wait for a custom ROM.
It helps using a taskiller + cache cleaner, but only for a short time
DocRambone said:
Use autokiller (free on market), it can adjust the android memory config settings.
Functional on LG 2x (root needed)
Click to expand...
Click to collapse
Will try
Do you have some settings for the app, that would be good with the o2x?
Haven't tried this exact app before...
larsn84 said:
Dunno if this is possible, but when I think of windows computers back in the days, it was possible to use som of the harddrive as allocated memory.
Click to expand...
Click to collapse
I think that Android has a better (and more specific) memory management technique.
Btw the method you are referring to it's called virtual memory and every modern general purpose operating system uses this memory management technique.
larsn84 said:
It helps using a taskiller + cache cleaner, but only for a short time
Click to expand...
Click to collapse
Task-killers aren't good with 2.2.2
There's a long explanation as to why, which can be googled.
Just a thought about memory utilization....
So Oneplus 3 is the first mainstream (not the first overall) android phone with 6Gb. Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones. There is really no point in wasted RAM. Having a lot of open apps in memory is truly great and could be the best use for it, but it also can present some issues. Background apps on android are not always suspended in the best way and can waste resources (CPU, battery). Of course if app and system are optimized correctly this shouldn't happen, but unfortunately it is not always the case. While google optimizes the system with dose features etc, I'm wondering about a simpler option until the better one is built into the system.
RAM is 10 times faster than storage, so why not use a portion of it as a RAMDISK, like in old days (MS DOS times). For those who don't know, RAMDISK is a portion of RAM that is used as a temporary storage (like flash memory), that will be 10 times faster than permanent flash storage.
Basically out of 6Gb RAM that phone has (Oneplus 3), 3Gb would be used as regular RAM and 3GB would be used as a RAMDISK. RAMDISK completely looses all the data after reboot, but the good thing is that phones don't really need to be restarted often. So RAMDISK would be almost permanent. Lets say you have 100 apps on your phone. Out of those you use 30 all the time. It is a bit inconvenient when app that you use often (for example Facebook) is kicked out from the memory and has to reload from flash storage (slow). Instead you could have those 30 apps to be loaded/copied/synchronized to the RAMDISK during initial boot. If app is kicked from regular RAM and needs to be restarted/resumed it would load 10 times faster from the RAMDISK. During regular intervals and before reboot data/cache from RAMDISK can be permanently saved (synchronized) back to the flash storage. If you have your favorite app that keeps misbehaving in the background (uses too much CPU, doesn't let phone to go into deep sleep and kills battery) you can just have it removed from background processes (swipe away, greenify, kill it etc), but then it will be almost instantly reloaded from RAMDISK when you need it later. So in the end you would have all your favorite apps loading super fast, even if it is not currently running in the background. You would sacrifice some RAM for faster app loading, possibly also minimizing battery loss due to some bad apps.
My knowledge of Android system is very limited and I might be very mistaken regarding this option, it's implementation and benefits. I would love to hear what people with better knowledge can say on this topic.
Droff said:
Just a thought about memory utilization....
So Oneplus 3 is the first mainstream (not the first overall) android phone with 6Gb. Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones. There is really no point in wasted RAM. Having a lot of open apps in memory is truly great and could be the best use for it, but it also can present some issues. Background apps on android are not always suspended in the best way and can waste resources (CPU, battery). Of course if app and system are optimized correctly this shouldn't happen, but unfortunately it is not always the case. While google optimizes the system with dose features etc, I'm wondering about a simpler option until the better one is built into the system.
RAM is 10 times faster than storage, so why not use a portion of it as a RAMDISK, like in old days (MS DOS times). For those who don't know, RAMDISK is a portion of RAM that is used as a temporary storage (like flash memory), that will be 10 times faster than permanent flash storage.
Basically out of 6Gb RAM that phone has (Oneplus 3), 3Gb would be used as regular RAM and 3GB would be used as a RAMDISK. RAMDISK completely looses all the data after reboot, but the good thing is that phones don't really need to be restarted often. So RAMDISK would be almost permanent. Lets say you have 100 apps on your phone. Out of those you use 30 all the time. It is a bit inconvenient when app that you use often (for example Facebook) is kicked out from the memory and has to reload from flash storage (slow). Instead you could have those 30 apps to be loaded/copied/synchronized to the RAMDISK during initial boot. If app is kicked from regular RAM and needs to be restarted/resumed it would load 10 times faster from the RAMDISK. During regular intervals and before reboot data/cache from RAMDISK can be permanently saved (synchronized) back to the flash storage. If you have your favorite app that keeps misbehaving in the background (uses too much CPU, doesn't let phone to go into deep sleep and kills battery) you can just have it removed from background processes (swipe away, greenify, kill it etc), but then it will be almost instantly reloaded from RAMDISK when you need it later. So in the end you would have all your favorite apps loading super fast, even if it is not currently running in the background. You would sacrifice some RAM for faster app loading, possibly also minimizing battery loss due to some bad apps.
My knowledge of Android system is very limited and I might be very mistaken regarding this option, it's implementation and benefits. I would love to hear what people with better knowledge can say on this topic.
Click to expand...
Click to collapse
Never mind, wrong post.
gee2012 said:
Did you read this http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/.
Click to expand...
Click to collapse
It is not about fixing the number of apps that can be held in memory, it is about different use for the RAM. When you have 40 apps in the background some of them can kill the battery. That is probably why Oneplus limited the number of apps. RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Droff said:
Did you read the post? It is not about fixing the number of apps that can be held in memory, it is about different use for the RAM. When you have 40 apps in the background some of them can kill the battery. That is probably why Oneplus limited the number of apps. RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Click to expand...
Click to collapse
I corrected my post didn`t i?
gee2012 said:
I corrected my post didn`t i?
Click to expand...
Click to collapse
I wrote reply while you did the correction. I think it is good to leave my reply there anyways, in case if someone else misreads the topic. Let me know if you think otherwise.
Droff said:
I wrote reply while you did the correction. I think it is good to leave my reply there anyways, in case if someone else misreads the topic. Let me know if you think otherwise.
Click to expand...
Click to collapse
Its cool
Droff said:
Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones.
Click to expand...
Click to collapse
Could you explain further why you think it is not being utilised ?
Droff said:
RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Click to expand...
Click to collapse
Android can not address any RAMDISK, it just makes no sense here.
One Twelve said:
Could you explain further why you think it is not being utilised ?
Click to expand...
Click to collapse
Look at the amount of free RAM in average use. There will be plenty that is unused. Keeping lots of apps cached is the best use for the free ram, but in some cases those background apps need to be removed from the active memory to prevent app from keeping device awake (and killing battery as a result). For example RAMDISK would allow to greenify all the bad written apps, stopping them from draining the battery, but then reloading them back to the active RAM almost instantly (much faster than from flash storage), when user wants to access the app again.
This situation (RAM "waste") can sure change with advances in android system itself, but as of now I just think RAMDISK is not a bad option for new devices with a lot of RAM onboard. Apparently we will see android phones with 8Gb Ram pretty soon.
dragon-tmd said:
Android can not address any RAMDISK, it just makes no sense here.
Click to expand...
Click to collapse
There is no such thing currently, but it doesn't mean that it cannot be created (at least in my understanding) and implemented via kernel or just an application (background service).
Here is info from WiKi
https://en.wikipedia.org/wiki/RAM_drive
Here are the examples of programs/apps for PC:
http://www.radeonramdisk.com/software_downloads.php
http://memory.dataram.com/products-and-services/software/ramdisk
Here some more info:
http://www.pcworld.com/article/260918/how_to_supercharge_your_pc_with_a_ram_disk.html
Plenty more can be found online.
I remember we used to do that on the HD2 - it was pretty cool!
blackalice said:
I remember we used to do that on the HD2 - it was pretty cool!
Click to expand...
Click to collapse
Pity it was just Windows Mobile OS.
Droff said:
Look at the amount of free RAM in average use. There will be plenty that is unused.
Click to expand...
Click to collapse
The impression i got that was not all that ram was not available and was reserved for the system. To the point one questioned that 6GB was available, felt like less.
How much RAM does the OP3 mention as free after a restart ?
One Twelve said:
The impression i got that was not all that ram was not available and was reserved for the system. To the point one questioned that 6GB was available, felt like less.
How much RAM does the OP3 mention as free after a restart ?
Click to expand...
Click to collapse
It shows about 4.5Gb free. I'm yet to fully test OP3 and see my average memory usage, but I doubt that I will have less than 2Gb free
Droff said:
It shows about 4.5Gb free. I'm yet to fully test OP3 and see my average memory usage, but I doubt that I will have less than 2Gb free
Click to expand...
Click to collapse
4.5GB free implies its working as stated.
You're saying in use that memory gets reserved and drops, that is more than it should.
Do u have any ideas how can that be done?
Sent from my HTC 10 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
That would be really cool
Sent from my HTC 10 using Tapatalk
Xperia U Lover said:
Do u have any ideas how can that be done?
Sent from my HTC 10 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
That would be really cool
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
As far as I know, there is no RAMDISK app for android at this time. I would love try it out myself. Unfortunately I don't have much coding experience to create this app (or kernel).
On a side note, after more time with a 6Gb phone I can see that this RAM can get utilized quite a bit. After editing the build.prop to magical number 42 and running bunch of apps (regular operation, nothing really extreme), the free cache reported by OS (developer options) is 1.2GB - 1.3GB. at the same time in RUNNING SERVICES it shows 2.8GB free. SYSTEM got bloated to 2.0GB
From what I can see, the apps that I use didn't misbehave so far and even with such heavy load on RAM, my battery didn't take a hit. As a matter of fact I'm very surprised by battery performance so far, but I'm only 1/4 way through.
That being said, I would still love to create 2Gb RAMDISK from that 6GB and play with it more.
Man your battery life is really good!
Sent from my HTC 10 using Tapatalk
Actually, my RAM is well used and i am grateful for having 6 GB in the phone, that is, because i am using two profiles and on 4GB phones they were always operating at the limit. with the oneplus 3 finally this is over.
Praise the lord.