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.
After fixing some lags with I/O system by using filesystem LagFix I still have a Lag problem in my system and I think it's not related to Samsung.
I think this could be an Android problem.
After a fresh reboot I get 124MB of free RAM.
BUT... every day I need to reboot the phone because after 3 hours it became laggy.
Now I analysed this and read a bit about the memory management on several forums and was able to reproduce the lag 2minutes after reboot.
I just need to use much applications one after another to raise the RAM usage for every application.
When the free RAM reaches 40MB I think the system clears some pieces for using it for the app I now want to use and there is the LAG.
Is there any fix for Android not caching every activity of an application in the RAM?
Now for me Android feels like: Usage -> Full RAM -> Lag
Sorry for the new thread but after 2 hours of research I didn't find anything useful over search function.
Yea, every program should have as much ram available as their size. 2gig for program storage on sgs, so there should be the same amount of ram ;D Anyway, theres still less memory for programs on the sgs than for example in the N1. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Sent from my GT-I9000 using XDA App
Not just the RAM for the apps... there's much more...all mails from internet, all google talk conversations, the wather I checked out from internet with any widget, feels like every interaction is cached into the RAM until it reaches the 40mb mark and after that every interaction on my system is laggy... for example: opening the notification bar needs 2-3 seconds.
I already talked to N1 users with the same problem
DasLeo said:
I already talked to N1 users with the same problem
Click to expand...
Click to collapse
Heading out the door in a minute so can't comment on the rest, but I strongly disagree with that part of your statement.
As an N1 owner I've NEVER seen lag like I suffer on the SGS. Never seen the absolute FREEZE in the GUI like the SGS gets.
I'm running FroYo on the N1 now, so can't compare side-by-side to the SGS things like memory usage, but I don't think that's the issue here if you're going to use the N1 as a comparison, despite other users complaining of lag.
You might try Autokiller or the free memory manager app from the Market and see if that improves thing, they'll keep more or less memory free depending on settings. You could test how soon lag comes with default, minimal, and aggressive settings.
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
rkantos said:
. I'd say there is about 384MB of ram total on the sgs and not the 512 claimed.
Click to expand...
Click to collapse
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Guys please,
Getting off-topic here. Here is Android Development.
Not Q&A or General.
Please post in the right section.
Here is getting too many off-topics that pose no relation to Android Development.
Too cluttered.
Thanks
DasLeo said:
DAMN!!! Nice app... it does exactly what I need cleans my RAM so I'll get 120MB and after that loading of apps is much faster than starting apps with Android included RAM cleaning.
It just cleans my RAM like a reboot but without the reboot
This should be a temporary solution until someone finds a better solution or until froyo is released.
I would like to have an application like this with an autoclean option on 2 hours
Click to expand...
Click to collapse
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
I use Memory Booster Lite (free version) app to free up memory, must do that manually but it works very well, if you buy the app it free up memory automaticly.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
The phone does have 512mb of ram. It just isn't used properly.
MOJO783010 said:
Hi, didn't read all the posts, but u should look into the RFS file system, which is samsung proprietery file system. It has a very bad implementation on android (i could be wrong). As for ram, the phone has 512 mb, but 128 are reserved for Gsm/data connection. Just think if you had an incoming call and all your ram was in use, u had to wait for the system to clear up some memory before being able to receive the call physiclly. That would be a long wait.
I could be wrong and sorry for the bad english.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, wrong. The reserved ram is in the form of a ram disk, which seems to be a bit oversized. Not really sure why a ram disk is needed at all, personally.
sammy555 said:
Auto killer is better.Its exactly the same as minfreemanager but can be made to apply at boot.Minfree manager resets itself at boot.
Click to expand...
Click to collapse
This is the correct solution. the JF* series of firmwares have very bad default settings for killing unused apps. Use this app to set them a bit better and you shouldn't have any problems.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
It does have 512 of ram, but some is partitioned off for the phone, so that you can always receive phone calls. Just about every device does this, because users would be more upset if they couldn't pick up the phone until they had closed a bundle of running programs. Don't you think that people here would have noticed earlier if the SGS physically had less ram than claimed ?
As far as the OP is concerned, sounds like you are just running too many programs at once. Its not an android problem, its user error.
Any task manager, but particularly an auto-killer will set you right, although alternatively you could try not leaving every app open when you're finished with it. You think your PC would run ok if you left one game open while you opened another ?
DasLeo said:
I never testet Froyo because everyone said, it's unstable but for me it seems like froyo has other RAM management than Eclair when you said you can't reproduce this problem.
I'm already using a task killer... I have my main apps ignored or excluded and most time there are 2 or 3 apps which will be killed after lock or time or what else.
What's the problem here... if I would use a PC with 512MB RAM and use only 10 small applications, it won't cache everything in the ram until it's full.
Click to expand...
Click to collapse
I wasn't comparing a N1 on FroYo to the SGS on Eclair. My comments were in regard to when I was on Eclair, which was several months...FroYo's only been available for a couple of months. What I said was since I'm on FroYo now, I can't compare side-by-side, but my experience with an N1 on Eclair was never any lag problem or GUI freezes.
Anyways, I also suggested you try Autokiller, and you missed that or misunderstood it by saying you already run a Task Killer (which is generally considered a bad idea, but I see you picked up on Autokiller after someone else suggested it. Enjoy.
Pika007 said:
If this turns out to be true, samsung is up for a massive lawsuit from MANY angry customers who've been mislead due to false marketing
Click to expand...
Click to collapse
Nah, all phones advertise the actual chip size in it, not the amount the system actually lets you use.
tra33372 said:
Have you ever tried "Minfreemanager" app?
It can change the minimum available memory level in different app usage.
The device must be rooted first.
Then select "Aggressive" preset and see the result.
Click to expand...
Click to collapse
Thank you. This removes almost all lag I'm experiencing.
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
Hello!
Welcome all galaxy s and android owners Im quite new to this hardware and software, in fact i spent all weekend trying to understand this machine...
Eventually, i fixed 3-combo bug, updated android from 2.1 to 2.2.1 JPU and applied speedMod from here:
http://forum.xda-developers.com/showthread.php?t=822756
And im wondering, do i really have so much ram? I have system info widget, it shows only about 150-190, on android 2.1 it was about 120-160, everything looks like my galaxy s has only 256 MB of memory (i just cant believe that) :O How can i check it more accurately?
Hey mate,
The reason why you can only see 339mb (or there abouts) of ram free is because the OS reserves some space for critical system apps.. Imagine if you couldn't receive calls because your live wallpaper and that game you are playing was using up all your ram.
Hope this answers your question,
Alex
Remember: If I have helped you please click on the "Thanks" button on my post
Sullson said:
Hello!
Welcome all galaxy s and android owners Im quite new to this hardware and software, in fact i spent all weekend trying to understand this machine...
Eventually, i fixed 3-combo bug, updated android from 2.1 to 2.2.1 JPU and applied speedMod from here:
http://forum.xda-developers.com/showthread.php?t=822756
And im wondering, do i really have so much ram? I have system info widget, it shows only about 150-190, on android 2.1 it was about 120-160, everything looks like my galaxy s has only 256 MB of memory (i just cant believe that) :O How can i check it more accurately?
Click to expand...
Click to collapse
By right our phone has 512MB.
However, some of the memory needs to be use for critical applications (e.g. running the phone etc.) therefore we are not able to unlock all 512mb for our use.
What you are able to see (since you're using SpeedMod kernel, it will be 339MB) is the memory available for OUR use. Do note that our phone needs to use part of that 339MB RAM to load up applications/boot up therefore you would not get 339MB free (rather about 120MB free ++ out of 339)
SXTN said:
Hey mate,
The reason why you can only see 339mb (or there abouts) of ram free is because the OS reserves some space for critical system apps.. Imagine if you couldn't receive calls because your live wallpaper and that game you are playing was using up all your ram.
Click to expand...
Click to collapse
Actually, that's a common assumption I hear which gets thrown around here but has never actually been proven. Apparently it's a memory hole, which means devices are using it. If it were reserved for apps, it would probably still show up in total RAM. Remember, Android is smart enough to kill apps as needed when more ram is required. Furthermore, freeing RAM doesn't take much work. So this explanation doesn't make much sense imho.
The reality might actually be that Samsung haven't had time to dynamically allocate the space with their drivers, so they took a shortcut until they had time to optimise.
Regardless of amounts I can say that 2.2.1 is the first firmware where memory management does not appear to be an issue.
Ok i found out that i actually have 339 Mb of memory. The problem is that all the time at least 130 mb are in use. I think that all the stand by android and samsung apps should work on the memory that stands in 512-339 and it shouldnt take my memory space. I saw 339 in task manager, also over there i see that samsung "steals" from it about 130. In addition it process running i see only about 30/40 memory in use. Android takes 16 mb. Any1 can explain this to me?
my phone showing only 304MO of RAM. Why?
Read what i did. U dont have speedmod. But what about my 130 lost memory...
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!