Related
Anyone know (with our phones running 2.2) what the optimal heap size should be? The leaked 2.2 came with 24m preset. Some ROMs run 32m. Bigger always seems better, but I've been reading other sites/forums and get conflicting thoughts.
That's why I thought I'd ask here.
I ran Linpack with both and average about 37.5 - 37.9 with either 24m or 32m.
I ran a few test increasing it to 48m and seen a decrease in performance. Bigger does not me better. I can not speak for anyone else but the best results i've seen was on 32m
theoneownz said:
I ran a few test increasing it to 48m and seen a decrease in performance. Bigger does not me better. I can not speak for anyone else but the best results i've seen was on 32m
Click to expand...
Click to collapse
same here, 32 seems to be the optimal size for me, I didn't see any difference with linpack but my quadrant went up when I set the heapsize from 24 to 32
Is there a way to patch the original leaked 2.2 to run its vm heap size at 32m?
I have my vm heap at 40 amd it runs smooth
Sent from my ADR6300 using XDA App
xvenom89 said:
Is there a way to patch the original leaked 2.2 to run its vm heap size at 32m?
Click to expand...
Click to collapse
Like to find this out myself. I've seen that this can be modified in the Cyanogen rom using Rom Manager, but not sure how this can be done via stock 2.2 rom.
I am by no means "good" at android yet, but im pretty sure there is an option to change the vm heapsize in build.prop in the /system directory. Just use adb to pull the one on there and then push the edited one (that u edit urself) to the phone. Also from what i can remember reading the heapsize basically is just how much ram/memory an app is allowed to use before android has to start "trash collecting" or "tidy up" the app usage. Setting it low will give the best linpack scores i think, but it will completely screw up regular app usage. Best to keep it at default to 32 imo. Setting it higher really wont do anything i dont think except maybe boost ur quadrant score but that may not transfer over to real app usage. My .1 cent
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
That is what u would be editing in your build.prop
chris61292 said:
I am by no means "good" at android yet, but im pretty sure there is an option to change the vm heapsize in build.prop in the /system directory. Just use adb to pull the one on there and then push the edited one (that u edit urself) to the phone. Also from what i can remember reading the heapsize basically is just how much ram/memory an app is allowed to use before android has to start "trash collecting" or "tidy up" the app usage. Setting it low will give the best linpack scores i think, but it will completely screw up regular app usage. Best to keep it at default to 32 imo. Setting it higher really wont do anything i dont think except maybe boost ur quadrant score but that may not transfer over to real app usage. My .1 cent
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
That is what u would be editing in your build.prop
Click to expand...
Click to collapse
Modified and updated.
I had a feeling it was the build.prop file I needed to edit.
Thank you sir!
But remember that bigger is not alwaus better. Im ising 40m and it is not better or worse than 32 or 24.:although i did notice some nice difference in the general speed of the os itself
chris61292 said:
I am by no means "good" at android yet, but im pretty sure there is an option to change the vm heapsize in build.prop in the /system directory. Just use adb to pull the one on there and then push the edited one (that u edit urself) to the phone. Also from what i can remember reading the heapsize basically is just how much ram/memory an app is allowed to use before android has to start "trash collecting" or "tidy up" the app usage. Setting it low will give the best linpack scores i think, but it will completely screw up regular app usage. Best to keep it at default to 32 imo. Setting it higher really wont do anything i dont think except maybe boost ur quadrant score but that may not transfer over to real app usage. My .1 cent
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
That is what u would be editing in your build.prop
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
chris61292 said:
I am by no means "good" at android yet, but im pretty sure there is an option to change the vm heapsize in build.prop in the /system directory. Just use adb to pull the one on there and then push the edited one (that u edit urself) to the phone. Also from what i can remember reading the heapsize basically is just how much ram/memory an app is allowed to use before android has to start "trash collecting" or "tidy up" the app usage. Setting it low will give the best linpack scores i think, but it will completely screw up regular app usage. Best to keep it at default to 32 imo. Setting it higher really wont do anything i dont think except maybe boost ur quadrant score but that may not transfer over to real app usage. My .1 cent
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
That is what u would be editing in your build.prop
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=803470
chris61292 said:
I am by no means "good" at android yet, but im pretty sure there is an option to change the vm heapsize in build.prop in the /system directory. Just use adb to pull the one on there and then push the edited one (that u edit urself) to the phone. Also from what i can remember reading the heapsize basically is just how much ram/memory an app is allowed to use before android has to start "trash collecting" or "tidy up" the app usage. Setting it low will give the best linpack scores i think, but it will completely screw up regular app usage. Best to keep it at default to 32 imo. Setting it higher really wont do anything i dont think except maybe boost ur quadrant score but that may not transfer over to real app usage. My .1 cent
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=24m
That is what u would be editing in your build.prop
Click to expand...
Click to collapse
If you use Root Explorer (which is an invaluable app, IMO), then you don't even have to go through the trouble of adb push and pull. With RE, you an simply just edit the file and be done with it.
Does anyone else get that issue where the web browser closes for no reason (no error or anything) when heap size is set to 24m? Only when I switched to Sadowrom and changed the heap to 32m did it stop this annoying issue that was present in every rom that I've tried. It mostly happened on heavy script/flash websites so I assumed it was a memory issue (happened a lot on this forum as well). 32m should really be default, this seems like a common issue from what I've read.
blakeem said:
Does anyone else get that issue where the web browser closes for no reason (no error or anything) when heap size is set to 24m? Only when I switched to Sadowrom and changed the heap to 32m did it stop this annoying issue that was present in every rom that I've tried. It mostly happened on heavy script/flash websites so I assumed it was a memory issue (happened a lot on this forum as well). 32m should really be default, this seems like a common issue from what I've read.
Click to expand...
Click to collapse
From what I've seen, the common denominator seems to be that the majority of phones experiencing this are overclocked. Some phones can handle it whereas others cannot. My last Inc would do this if oc'd to 1.15 but was fine at lower speeds. My current Inc rarely does this even when pushed to 1.19.
najaboy said:
From what I've seen, the common denominator seems to be that the majority of phones experiencing this are overclocked. Some phones can handle it whereas others cannot. My last Inc would do this if oc'd to 1.15 but was fine at lower speeds. My current Inc rarely does this even when pushed to 1.19.
Click to expand...
Click to collapse
Mine did it with 100% stock 2.1 and 2.2 w/ no root or overclocking and was actually the main thing that motivated me to install roms (my work bought me the phone so I was hesitant).
All kinds of apps close if I overclock it to unstable levels (AOSP goes unstable much more dramatic for me at 1.15, sense is mostly stable up to 1.19) but I believe this is a different issue. Bits are lost so apps go boom, much like the artifacts when I overclock my graphics card too far. Overclocking is the issue when other apps close as well but with the lower heap size only my browser closes after many days of up time without any other issues. I have no issues since heap has been 32m, it would happen daily at 24m.
There is one website that can still bring it down however, that is viewing the full google images page. It seems to have a recursive issue where things load over and over again and the browser eventually vanishes. I can load 500 page pdf files and run stress tests all day and never get them to close or error so I'm pretty sure it's a browser specific issue (does it in all other browsers that I've tried as well).
martino2k6 said:
http://forum.xda-developers.com/showthread.php?t=803470
Click to expand...
Click to collapse
thank you!
I changed the build.prop, but left the 'm' off at the end of the line, now it won't boot up. I can adb shell into it, adb pull, but su doesn't work, segfaults, can't push the file back to /system. How do I fix it??
EDIT: These settings don't seem to be read by the lowmemorykiller process, so they have no effect. But the app Autokiller modifies the settings in /sys/module/lowmemorykiller/parameters/minfree and that one works!
Hey guys, I just noticed this thread and it's very interesting.
http://forum.xda-developers.com/showthread.php?t=622666
Android has its own low memory task killer, and it can be configured. I checked the defaults for my JPC Froyo firmware, and it was set a bit low, meaning processes are not killed as soon as they should be.
I also think I've found a new way to configure those options:
I modified my /system/build.prop file and added the following lines.
# tune the lowmemorykiller
ro.FOREGROUND_APP_MEM=5120
ro.VISIBLE_APP_MEM=8192
ro.SECONDARY_SERVER_MEM=12288
ro.BACKUP_APP_MEM=12288
ro.HOME_APP_MEM=12288
ro.HIDDEN_APP_MEM=20480
ro.CONTENT_PROVIDER_MEM=22528
ro.EMPTY_APP_MEM=24576
Reboot for it to take effect.
These values are twice my original ones. You can check current values by doing a "getprop".
NOTE that these values are in PAGES (4K). So 24567 pages = 98,304 KBytes.
Strangely the /sys/module/lowmemorykiller/parameters/minfree values are not changed. But I think the lowmemorykiller might be reading the prop values directly. I'm running many programs now trying to hit the limit and see if it takes effect.
EDIT: It seems to be working! I can run many many apps and the phone remains responsive. Unused apps are killed as needed. Check out the screenshots below:
Is this Froyo specific or does it also apply to Eclair?
Edit: Never mind
Isn't this pretty old news?
Aren't there are apps in the Market for this (AutoKiller, MinFreeMgr)?
I guess if you know precisely the best settings for your own phone, putting them in a startup script makes sense. I didn't realize build.prop could be used to set things like that.
distortedloop said:
Isn't this pretty old news?
Aren't there are apps in the Market for this (AutoKiller, MinFreeMgr)?
I guess if you know precisely the best settings for your own phone, putting them in a startup script makes sense. I didn't realize build.prop could be used to set things like that.
Click to expand...
Click to collapse
MinFreeMgr tries to do the same thing but by editing a different file which doesn't stay on reboot. This build.prop edit is a new finding, and it seems to work. I think it could be a better solution as it stays after a reboot. The difference between this and other Auto Task Killers is that this is using Android's built-in memory management mechanism which is much smarter than any external task killer can be.
So far it works really well!
Can we convert this into a workable program?
Very interesting, will give it try.
hardcore said:
MinFreeMgr tries to do the same thing but by editing a different file which doesn't stay on reboot. This build.prop edit is a new finding, and it seems to work. I think it could be a better solution as it stays after a reboot. The difference between this and other Auto Task Killers is that this is using Android's built-in memory management mechanism which is much smarter than any external task killer can be.
So far it works really well!
Click to expand...
Click to collapse
Yeah, I acknowledged the build.prop was interesting, very interesting, actually. I wonder if you could set other parameters in there that some of the modders are throwing into init scripts and/or small apps.
For clarification, the two Market-available apps I mentioned (AutoKiller, MinFreeMgr), both do the exact same thing you're talking about. AutoKiller is poorly named, as it's not a task killer per se, it merely modifies on the fly the settings you're talking about here; same with MinFreeMgr. Both can be set to take affect at startup/reboot. Advantage, can be changed on the fly without reboot, disadvantage, another app to load during reboot.
Thanks.
distortedloop said:
For clarification, the two Market-available apps I mentioned (AutoKiller, MinFreeMgr), both do the exact same thing you're talking about. AutoKiller is poorly named, as it's not a task killer per se, it merely modifies on the fly the settings you're talking about here; same with MinFreeMgr. Both can be set to take affect at startup/reboot. Advantage, can be changed on the fly without reboot, disadvantage, another app to load during reboot.
Click to expand...
Click to collapse
Ah, thanks for clarifying that. I discovered those values when I did a getprop. The values I posted above (2x default) work okay. But now I'm trying slightly less aggressive values (1.5x) to see what might be the optimum - too much free RAM is also a waste.
By the way, what task manager is that your pics are of? Looks like the Samsung Task Manager, except the RAM tab. On mine, that tab's Summary and does not give the same info as yours. Mine's unchanged on the various firmwares I have used JG1, JG5, JM1, JM5, JM6, JH1, JM7...
distortedloop said:
By the way, what task manager is that your pics are of? Looks like the Samsung Task Manager, except the RAM tab. On mine, that tab's Summary and does not give the same info as yours. Mine's unchanged on the various firmwares I have used JG1, JG5, JM1, JM5, JM6, JH1, JM7...
Click to expand...
Click to collapse
You're right. Its the JPC Task Manager. It has those extra options to clear the memory. I don't use them now though.
With Eclair I have 326MB ram. Froyo has less just 304.
And after we speak for galaxy lag. I thing it is an android lag because the system to start cut ram from frozen apps and to give at the new application they try to open, the free ram must be 48mb.
Very less for the UI.
I am not happy. We let WM so as to don't need fixes and custom rom. And we have other problems.
I will give it a try. Already modified my build.prop and un-installed Autokiller. Will check for the next few days.
P/S: Probably due to placebo effect, but it feels more responsive.
If it works, this is a good hack!
distortedloop said:
By the way, what task manager is that your pics are of? Looks like the Samsung Task Manager, except the RAM tab. On mine, that tab's Summary and does not give the same info as yours. Mine's unchanged on the various firmwares I have used JG1, JG5, JM1, JM5, JM6, JH1, JM7...
Click to expand...
Click to collapse
That's the froyo task manager, which can be found in the earlier froyo (xxjp3) release as well.
If you want, i can attach this apk (either odexed or deodex, you pick) for you to try on eclair.
hardcore said:
Hey guys, I just noticed this thread and it's very interesting.
http://forum.xda-developers.com/showthread.php?t=622666
Android has its own low memory task killer, and it can be configured. I checked the defaults for my JPC Froyo firmware, and it was set a bit low, meaning processes are not killed as soon as they should be.
I also think I've found a new way to configure those options:
I modified my build.prop file and added the following lines.
# tune the lowmemorykiller
ro.FOREGROUND_APP_MEM=5120
ro.VISIBLE_APP_MEM=8192
ro.SECONDARY_SERVER_MEM=12288
ro.BACKUP_APP_MEM=12288
ro.HOME_APP_MEM=12288
ro.HIDDEN_APP_MEM=20480
ro.CONTENT_PROVIDER_MEM=22528
ro.EMPTY_APP_MEM=24576
Click to expand...
Click to collapse
Hey, I was thinking about this, and I started to do some research and found that for Froyo, other devices are using these as parameters:
ro.FOREGROUND_APP_MEM 1536
ro.VISIBLE_APP_MEM 2048
ro.SECONDARY_SERVER_MEM 4096
ro.BACKUP_APP_MEM 4096
ro.HOME_APP_MEM 1536
ro.HIDDEN_APP_MEM 5120
ro.CONTENT_PROVIDER_MEM 8192
ro.EMPTY_APP_MEM 10240
I'm just wondering if we should be increasing the memory sizes or decreasing them?? Maybe do a combination of both?? I gotta do more research, find out how each attribute behaves, and get more info before editing this stuff.
YG007 said:
Hey, I was thinking about this, and I started to do some research and found that for Froyo, other devices are using these as parameters:
ro.FOREGROUND_APP_MEM 1536
ro.VISIBLE_APP_MEM 2048
ro.SECONDARY_SERVER_MEM 4096
ro.BACKUP_APP_MEM 4096
ro.HOME_APP_MEM 1536
ro.HIDDEN_APP_MEM 5120
ro.CONTENT_PROVIDER_MEM 8192
ro.EMPTY_APP_MEM 10240
I'm just wondering if we should be increasing the memory sizes or decreasing them?? Maybe do a combination of both?? I gotta do more research, find out how each attribute behaves, and get more info before editing this stuff.
Click to expand...
Click to collapse
I think increasing is better if you want apps to be auto killed. The default values (for JPC at least) are half of what I suggested. And it didn't seem to be aggressive enough for the SGS.
hardcore said:
I think increasing is better if you want apps to be auto killed. The default values (for JPC at least) are half of what I suggested. And it didn't seem to be aggressive enough for the SGS.
Click to expand...
Click to collapse
Just a side topic, saw your CSC is OLBJG4, did you manage to flash and got it configured automatically, or that *#272*HHMM# still does not work, and you have to set the apn manually?
hardcore said:
But now I'm trying slightly less aggressive values (1.5x) to see what might be the optimum - too much free RAM is also a waste.
Click to expand...
Click to collapse
That's the mantra in linux "free memory is wasted memory."
I first saw this stuff discussed here. Probably nothing you haven't figured out yet.
I think the settings for any individual are going to vary; there is no set answer, too much of variable in how you use your phone and what apps you use, etc.
You might check out "AutoKiller", it's free, and has some presets, along with ability to roll your own settings. I'd play with it until I found the numbers I liked best, then you could bake them into your build.prop. That would save you the slight hassle of editing and rebooting.
You can also just echo them from the terminal app, but I'm sure you already knew that.
But for those who don't, here's a sample from the above linked article:
Code:
su
echo "1536,2048,4096,5120,15360,23040" > /sys/module/lowmemorykiller/parameters/minfree
Also, while you're playing with settings, have you also looked at changing the i/o scheduler. Lots of debate over what's best. Again, I think it just depends on how you as an individual use your phone...
g00ndu said:
Just a side topic, saw your CSC is OLBJG4, did you manage to flash and got it configured automatically, or that *#272*HHMM# still does not work, and you have to set the apn manually?
Click to expand...
Click to collapse
I sortof hacked it into my /system folder manually. Just need to replace some files there. Auto APN does work. Maybe I'll write up a procedure when I'm more sure of it.
Interesting. Keep up the good work!
hmm...what is the difference between setting it in build.prop vs setting it in autokiller?
Hi @all!
I had many different ROMs installed and 1 thing is driving me nuts on all:
The system is killing apps that I don't want to get killed at all, any time!
e.g.: FolderOrganizer (using folder shortcuts and notification item, but it still gets killed)
AutoKiller's ability to reduce oom-value isn't persistent - so no option.
I've found this:
http://lwn.net/Articles/317814/
To make some special apps invincible would do it for me, because most options in apps to hold them in RAM are quite buggy. (as they say)
Wouldn't this patch be great or have I missed something allready existing?
If so, plz give me a hint.
THX in advance!
Write a short init script, that set oom_adj to -17 and the app won't get killed. Or just set it manual in a terminal.
Hi!
I've tried that:
Code:
su
echo -17 /proc/'pidof com.abcOrganizer'/oom_adj
But after some time or screen on/off the oom-value isn't -17 anymore and it gets killed after some more time.
The "-17" doesn't lock it like in former kernel versions. (for what I have read)
Is there another way?
Can someone try to compile a kernel with the patch?
EDIT:
In GingerVillain 1.0 I cann't even adjust the oom_adj with the commands above.
floyd0815 said:
Hi @all!
I had many different ROMs installed and 1 thing is driving me nuts on all:
The system is killing apps that I don't want to get killed at all, any time!
AutoKiller's ability to reduce oom-value isn't persistent - so no option.
I've found this:
http://lwn.net/Articles/317814/
Click to expand...
Click to collapse
Floyd, I am looking for a solution to this too. Hate that Android kills my navigation in the backgroud silently. Also other apps. Please, tell me if you have found a way to "protect" an app from killing. Thanks for making this thread/topic! I think this matter id so important and I cant understand how no one is bother by this. I hate it just as much as you and I want to find a solution.
Simple use swap part you try?
Camogyp said:
Simple use swap part you try?
Click to expand...
Click to collapse
Please, tell me what you mean. Sorry... I don't understand. I really have to know Please, be more specific.
Thanks in advance!
Create a SWAP partition on the SDCARD, about 512MB should be ok. You shouldn't go under 256MB. Then use a kernel that supports SWAP
There's an option named "bulletproof apps" in the Supercharger v6 script that is supposed to keep apps in memory forever. You'll find the thread easily. If you want to try it, use the starter kit that you find there first as it needs to patch some system file for the script to work.
DeeDroid said:
There's an option named "bulletproof apps" in the Supercharger v6 script that is supposed to keep apps in memory forever. You'll find the thread easily. If you want to try it, use the starter kit that you find there first as it needs to patch some system file for the script to work.
Click to expand...
Click to collapse
andreigherghe said:
Create a SWAP partition on the SDCARD, about 512MB should be ok. You shouldn't go under 256MB. Then use a kernel that supports SWAP
Click to expand...
Click to collapse
Thank you, guys! Nice of you to help. One question: if I use Supercharger, is it going to create a SWAP partition itself, or I'm going to have to do that myself manually. Or in fact Supercharger doesn't even need SWAP partition? What's the most proper way? I already read about the Supercharger and I was thinking about using it.
Or in the end may be it would be good to go from the stock ROM to a private ROM, which has supercharger integrated? is there a good private ROM you would recommend having supercharger?
You dont need a swap partition, the easy way is to use a swap file. Swapper2 from the play store can do that if your kernel supports swap.
Swapping didnt help much for me with background apps getting killed to fast. Supercharger is a different thing that has nothing to do with swapping. I think its changing the OOM value of apps that have been bulletproofed periodically in the background so that Android kills something else on low memory but not the app you want to keep alive.
DeeDroid said:
You dont need a swap partition, the easy way is to use a swap file. Swapper2 from the play store can do that if your kernel supports swap.
Swapping didnt help much for me with background apps getting killed to fast. Supercharger is a different thing that has nothing to do with swapping. I think its changing the OOM value of apps that have been bulletproofed periodically in the background so that Android kills something else on low memory but not the app you want to keep alive.
Click to expand...
Click to collapse
DeeDroid, thank you very much for helping me again. I decided to install Supercharger.
Please, tell me one more thing: what is the swap going to help for. Is i good to also have it? Should I install both Supercharger and Swapper2 or if I have only Supercharger this would be enough. I dont want to overdo everything and pile my phone with apps. Thank you again.
Well the swap should compensate the rather low amount of physical ram, but don't expect too much, I didn't notice a big difference and apps were killed in the background anyway. You can just try it with swapper2. If your kernel supports it, it's as easy as clicking a checkbox on and off.
You can type "free" in the terminal to see if your swap file is beeing used and how much of it.
Supercharger and Swap do different things that shouldn't interfere with each other so you probably could use both at the same time I think. But as your primary goal seems to be to avoid certain apps being killed in the background I would go for the supercharger, though it's a bit more complex to set up. Supercharger is supposed to make the overall performance better, "bulletproof apps" is just an additional features. I didn't try it on my Desire but it helped a lot on my Archos Tablet that also got only 512MB RAM.
Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Personally I haven't had a low memory situation since I rooted and installed cm7, the app your talking about I have installed after reading one of your other posts about it, I presume that it would work the same way as juwes after setting the low memory values, I don't use those settings with it though as I have juwes script installed, the other tweaks seem fine but again I think I had some of them covered from editing my build.prop (still have work to do on that though) and a few other little things, I can't knock this app though as it does seem to have made my battery last a bit longer since installing yesterday, I'd personally rather change the settings myself than have yet another app doing it for me but until I figure which setting seems to be helping my battery out I'll keep it installed.
A couple of other apps which might help you keep it smooth,
Autostarts- I swear by this app its one of my best buys from the market, why use a task killer when you can just stop the app starting in the first place??
Fast reboot pro- after time apps hold memory which they don't really need, hit this and it'll quickly reboot everything (unless you tell it to leave something alone) freeing up spare ram.
Sent from my HTC Wildfire using xda premium
Cheers for info,really happy with this app at the moment.by the sounds of things its doing similar job to other script mods,which I can't get working cos of s - off issue. Posted this for s on users benefit. Hope it helps others.
Edit my settings. Read 1st post.
sent from my wilderbeast/buzz
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
The only problems I see with having higher settings are if it closes something you use regular it'll be slower to open that app, I'd rather keep them set low and have apps open quickly.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I agree but this app lets you temporary lower the oom level for apps,so I just lower oom on most important. Long click on process or service and to lower.
sent from my wilderbeast/buzz
Does it?..........I didn't spot that nice find!!
Sent from my HTC Wildfire using xda premium
Yep,long click app in service or process then choose to lower oom.it resets if you reboot so get your settings desired then leave by pressing home button.
sent from my wilderbeast:buzz
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
gozzaa said:
whats up with these settings for the pages? what do these settings change?
atm i have these settings:
2560
4096
25600
30720
40960
Click to expand...
Click to collapse
Change the view from pages to mb and these are the values when it will start killing processes etc. Ie. When your memory gets to the amount your phone starts freeing up starting with the highest setting (empty apps)
Its all explained above,just that you have the pages view instead of mbs.
Quote " its healthy to have enemies, it means you've stood up for something you believe in "
ahh the pagesettings are the same as the MB ones?
i thought its two different things
thanks for the explanation!
btw. do you still use the same settings?
Yes to this day I still use this app even though I'm now s-off with the settings I posted,I will just double check and ammend if needed on 1st post.
" once its gone,its GONE."
slymobi said:
am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Click to expand...
Click to collapse
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
i tried supercharger and juuwes but had issues which i think were specific to me but one of the issues was bootlooping from supercharger as well as other things. im not saying one is better than the other but as you and myself had issues with one of the mods then its an alternative for others to use. i prefer this as you get to control the settings and mods yourself from the app. also this is available for s-on whilst the others i believe need s-off.
zephyri-xr said:
I used to use that too and I felt some differance too but I think you have to open the program every boot. But some told me that it isn't just powerful as Supercharger so I deleted the optimiser and tried Supercharged and got a bootloop instead. I didn't get it to work but I believe that Supercharger is a better solution.
Click to expand...
Click to collapse
I got a boot loop from supercharger. I had to wipe my phone and start again from an RUU as all my previous backups became corrupted. Nightmare. TBH in the few days that it did work, i saw/felt no difference.
Using CM_7.1.0.1 probably wouldnt advise to use the supercharge, CM_7 minfree values are set to a pretty good level to keep things in order i think
slymobi said:
Hi i found an app called auto killer memory which ive been running for a while. this app has worked wonders for my wilderbeast, its on fire. so ive been tampering alot with things but this seems to have stabalised my phone loads. presets i set to lost, enabled advance mode,apply at boot,ticked all system tweaks and of course when promted enabled super user. my phone is now running sweet and battery has improved too. i dont know if this makes any sense but i have noticed a difference. whoop whoop. am i over optimistic that this works the same as the v6 super charger/juwes ram optimiser ???
Ok I've ammended my settings within this app after doing some research And in memory values I'm now running at 6/10/16/100/120/160 to keep my phone running snappppppy. To explain the values in brief...... if free memory goes below 160mb my phone starts to kill empty apps etc etc as free memory goes below next value the phone starts to kill corresponding apps. Kind of makes sense to me now. Ok I know my settings makes the phone kill more frequently but its damn snappy now,and it can lower the oom settings by long pressing the app in processes section you wish to lower and choosing lower oom. Lowering the oom basically gives the app less chance of being killed.
Click to expand...
Click to collapse
I have tried supercharge script and does make phone smooth. Also Ive use ram manager new app and that too made phone smooth. But this app (Pro) is so far great. I tried out your settings for now to see if it suits me and had the app for an hour and the phone is very snappy and smooth (which is most important to me). I hope there is a slight battery improvement that many have said on the net but will test more and will leave feed back. A big thx m8!
no probs mate, like i said i have tried the lot and this one for me is really good and you get to be the controller lol.the only drawback i have noticed is that it takes a little longer for the phone to boot after a reboot but !!!!! im ok with that.
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
eventcom said:
LMFAO looks like I didn't pay enough attention... I've used a lot of tweaks already to make my Willy faster, more snappy and stable but to be honest nothing gave it such a boost like that
BTW: are you still using the settings of the op?
Holy crap, I've read that really often here and elsewhere but it's the first it applies to myself: feels like a new phone
Click to expand...
Click to collapse
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048.
Say oooh la la
slymobi said:
I use aggressive setting mostly, all advanced tweaks except sdcard boost one as this bumps read ahead up to 2048, just my preference you might prefer 2048
Click to expand...
Click to collapse
I see. I just have to sort things out now. Regarding the SD card read - I have it already done by sdbooster (@2048) - I'm at a point where I should make a documentation to stay on track and to avoid double tweaks lol.
I'm also very interested into scratch's build.prop lol (guess that would help to drop even more tweaks). Thx again - I've not forgotten about your tip re. AMO - just shifted it too far lol.
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Djalaal said:
Perhaps you can noobify that a bit, lol. I had to google almost everything you mentioned. As I understand it, this Synapse allows you to tweak the kernel? And this KSM settings can improve this RAM issue? Care to elaborate? And what is laptop mode?
I've read about adjusting the LMK values to calm LP down a little. Any idea though why this was so necessary in LP, but not in KK? Is stock LP 'naturally' more RAM hungry than KK?
Click to expand...
Click to collapse
I can try to elaborate little bit, as Ive been flashing things and researching xda a lot, but I am still noob in how/why things are the way they are. From what I gather lollipop just handles memory differently then kk did. I think that is some of the reason as to why the "recent apps" persist through reboots now. Remember, our device was not really supposed to run kk and certainly not meant to run lollipop. The developers here are without a doubt amazing in what they know and what they do for us users. A new kernel and driver was necessary to run lollipop on the aging gnex. Now, some of the issues we are experiencing is a google issue and will only seem to get fixed when they get around to it. I know my nexus 7 (old) has some memory issues and lag and redraws from time to time....not as much as I noticed with my gnex before the changes were made I stated in the above post. I recently helped my friend root and upgrade his oneplus one to lollipop and he has the same issues we all have, maybe not as bad, but they are noticeable
A lot of the questions you have, have been discussed recently in bsmitty83 kernel thread, since I asked them. There are links there as to what KSM and laptop mode are and what they do. KSM-kernel same page merging helps with RAM and I believe laptop mode helps to conserve power. A lot of these things are geared at devices with low ram like the aging gnex, but the developers have done a great job at making lollipop a daily driver. Most users I think use trickstermod from playstore to tune kernel settings, and that is ok, however, you must purchase the paid version to tweak low memory settings, which I did. However, synapse, also found on playstore can also be used to tweak kernel settings, but the kernel has to contain UCI support for the synapse app to work. Synapse has more settings available to tweak than trickster does, like KSM and laptop mode, which have helped me very much. The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work
Hopefully this was rather accurate and helpful and not convoluted! ha.....im sure some more knowledgeable people will come and correct anything I said that may be incorrect, but in the meantime, read through the R10 kernel thread and see what you come up with
What ROM and kernel are you currently using?
Thank you
erk1725 said:
...
The only kernel I'm aware of that has UCI support for synapse is bsmitty83 Full_Auto R10, because osmosis made it work.
...
What ROM and kernel are you currently using?
Click to expand...
Click to collapse
I'm currently using AOSP rom (by freshgimmi) and the Full Auto R10 you mentioned. I'll try injecting the new ramdisk now and see how it goes.
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Djalaal said:
Does this even need an explanation? Lollipop kills apps like it's his hobby.
Even with only a few light (on RAM) user apps running in the background you sometimes find yourself staring at your launcher home screen that, you could've sworn, was just showing a different app a second ago.
Or the times when, after multi-tasking a bit, your phone starts becoming painfully slow. Turns out that some apps are so stubborn that they go on strike (continuously restarting) when LP kills them.
I'm sure many have experienced this. And I have seen some devs address this issue here and there. I though it would be useful to gather the info into one thread, to ease our (or my?) frustration on this issue.
What I wanna know is, what causes it exactly (why didn't it happen on KK?), and is there a solution to this? Or at some way to calm LP down a bit with his killing of innocent apps.
Thanks.
Click to expand...
Click to collapse
SpideyTheMan said:
I noticed this issue as well for the first several days . However once I installed the new bootanimation from arter97 the issue doesn't occur anymore. Not sure if it's related but all I did was mount /system as rw and copied into the new lollipop boot animation from here: http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
Click to expand...
Click to collapse
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Okay, you're right. As a test last night I switched from FML 5.0.2 to LiquidSmooth's LP ROM and I'm not seeing any aggressive app kills in LiquidSmooth.
Djalaal said:
I know about this issue. It is a memory leak during boot. It is a good catch, though all you're changing is the bootanimation.zip. AFAIK, it should not affect your system's performance after boot, once your phone is up and running. My issue is a different thing entirely. I never got bootloops (that is, when not messing around with xposed).
Click to expand...
Click to collapse
erk1725 said:
Im running 1/8 FML with synapse injected R10 kernel on my toro and with ksm and laptop mode enabled in synapse, I haven't had a launcher redraw in days. I don't have anything whitelisted either. However, the trade-off I have at the moment is I cant seem to stream videos on my stock browser. Havent tried a different browser or anything. I just uncheck those two settings and reboot and all is well, but my phone certainly works much better now, and no redraws, with neph settings for LMK
Hope something helps someone!
Thanks
Click to expand...
Click to collapse
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Djalaal said:
I have got synapse up and running. I AM wondering though, what LMK settings are you using? Cause the neph settings I know of tell me to set empty app to 370, but synapse only allows max 320... If you're following different settings, could you link the post for me?
Click to expand...
Click to collapse
Glad you got everything up and running.....Im using Neph's settings for LMK, and your correct the empty app only goes up to 320 in synapse. There was a post somewhere where Neph said he was still tweaking his LMK values and I believe he mentioned about lower empty app to 330 or something, so I just set it to 320 in synapse and call it a day