Develop Bugs

[Q] RAM availability varying figures

Ok so in the BLISS beta thread there was some discussion about available RAM. To keep that thread clear of our BS i decided to post this up for us.
I do recall Tiny mentioning something in the Bliss thread about us needing to read into Android Memory Management so I took a peak using trusty old Google and didn't find too much, then again I am at work. I'm sure there is more to It than I have stumbled upon though but I didn't want us to continuing threadjacking.
Anyway, Bob was posting how he had this amount of RAM available that we thought was unheard of. Upon further investigation, I believe the app he/she is using is pulling up data from here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While most of us have been using task manager in the notification pulldown to see this:
Those screens were taken literally less than a minute apart. Why do these figures vary so much? I have no clue.
Discuss.

Marcismo55 said:
Ok so in the BLISS beta thread there was some discussion about available RAM. To keep that thread clear of our BS i decided to post this up for us.
I do recall Tiny mentioning something in the Bliss thread about us needing to read into Android Memory Management so I took a peak using trusty old Google and didn't find too much, then again I am at work. I'm sure there is more to It than I have stumbled upon though but I didn't want us to continuing threadjacking.
Anyway, Bob was posting how he had this amount of RAM available that we thought was unheard of. Upon further investigation, I believe the app he/she is using is pulling up data from here:
While most of us have been using task manager in the notification pulldown to see this:
Those screens were taken literally less than a minute apart. Why do these figures vary so much? I have no clue.
Discuss.
Click to expand...
Click to collapse
Hmmm. Weird, I am currently downloading the rom. Perhaps sense is using a different amount of RAM than the rest of the OS is.
I'm sure we will have closure on this in the next release from the developers.

Marcismo55 said:
Ok so in the BLISS beta thread there was some discussion about available RAM. To keep that thread clear of our BS i decided to post this up for us.
I do recall Tiny mentioning something in the Bliss thread about us needing to read into Android Memory Management so I took a peak using trusty old Google and didn't find too much, then again I am at work. I'm sure there is more to It than I have stumbled upon though but I didn't want us to continuing threadjacking.
Anyway, Bob was posting how he had this amount of RAM available that we thought was unheard of. Upon further investigation, I believe the app he/she is using is pulling up data from here:
While most of us have been using task manager in the notification pulldown to see this:
Those screens were taken literally less than a minute apart. Why do these figures vary so much? I have no clue.
Discuss.
Click to expand...
Click to collapse
Very good idea by the way. I can't actually answer why the two screenshots are different other than to assume where they get their information is obviously different as the free RAM is not going to vary that way. I actually never care about memory too much as long as the ROM runs smooth. It sounds like people are benchmarking using free RAM which is totally dependent on what apps you have running and in fact installed. Read on if you're still curious.
Let me try to summarize from what I understand. Basically from what I found by googling the Android OS does memory management different than Windows. More total RAM is definitely better in both scenarios as you can run more apps before the system has to load them to RAM. However, Android loads apps in memory at boot so having more apps could cut back on memory and I think it learns what is more popular on usage and prioritizes those. If you go killing apps, it may just reload them, using more battery than leaving them running, or they may stay stopped. I think the task manager should be used in a similar instance to Windows like if you have an app that's not responding or frozen. The lag actually stems from background processes such as reloading apps that it suspends from RAM. If you are having lag issues from low RAM (I would say around 50 MB reported in task manager though 60-70 MB could start leading to lag), I might be able to do something to assist with the lag on the kernel side. I can't promise this before the source is released. I actually don't plan new features until HTC releases source, just bugfixes if there are any (besides the unfortunate issue with USB mounting on some ROMs).
I'm aware that Sense uses more RAM and basically swap support could be added on the kernel side to allow virtual RAM and it should hopefully be smoother.
Sorry if I got too technical.

tiny4579 said:
Very good idea by the way. I can't actually answer why the two screenshots are different other than to assume where they get their information is obviously different as the free RAM is not going to vary that way. I actually never care about memory too much as long as the ROM runs smooth. It sounds like people are benchmarking using free RAM which is totally dependent on what apps you have running and in fact installed. Read on if you're still curious.
Let me try to summarize from what I understand. Basically from what I found by googling the Android OS does memory management different than Windows. More total RAM is definitely better in both scenarios as you can run more apps before the system has to load them to RAM. However, Android loads apps in memory at boot so having more apps could cut back on memory and I think it learns what is more popular on usage and prioritizes those. If you go killing apps, it may just reload them, using more battery than leaving them running, or they may stay stopped. I think the task manager should be used in a similar instance to Windows like if you have an app that's not responding or frozen. The lag actually stems from background processes such as reloading apps that it suspends from RAM. If you are having lag issues from low RAM (I would say around 50 MB reported in task manager though 60-70 MB could start leading to lag), I might be able to do something to assist with the lag on the kernel side. I can't promise this before the source is released. I actually don't plan new features until HTC releases source, just bugfixes if there are any (besides the unfortunate issue with USB mounting on some ROMs).
I'm aware that Sense uses more RAM and basically swap support could be added on the kernel side to allow virtual RAM and it should hopefully be smoother.
Sorry if I got too technical.
Click to expand...
Click to collapse
Not technical enough for me. I'll eat up as much info as you wanna dish.

loonatik78 said:
Not technical enough for me. I'll eat up as much info as you wanna dish.
Click to expand...
Click to collapse
Ok, we'll see. This is all from memory. Maybe I'll try again but I'm tired. I might have to do some more research.
Oh, I forgot, the Inc actually has 512 MB of RAM but about 100MB of it is dedicated to the kernel and OS processes that cannot be used by apps and such including the homescreen app. Google wasn't too helpful but this is just from my observations.
If anyone has more information please share as I'm curious why task manager is different than the RAM shown in running. I know there is a command in Linux called free that can be run from terminal emulator but it doesn't report accurately what is available for the system.
Sorry I need sleep so that's all for tonight.
As far as developers knowing, I think the CM devs would be knowledgable on this subject as they see the inner workings of Cyanogenmod and the AOSP framework so they see the source code of Android which is not available for the Sense framework.
FYI, CUViper is one of the maintainers for the Inc for Cyanogenmod so he oversees code changes for the Inc and I know he has also worked on the kernel for Cyanogenmod.

For what it's worth - system panel reports about the same as task manager for me (around 95mb) - and my running apps screen shows a huge amount of ram free - 288mb at the moment

Thank for breaking it down the best you can Tiny.
I don't have the greatest amount of computer knowledge but when I think if scarce free RAM I think that would contribute to a slow running system but I wasn't aware that Android handles memory so much differently but I guess that's why people were starting to have issues with Synergy due to the cache partition filling up with memory from apps? I read users of Synergy were having issues with the ROM becoming unstable and it was necessary to clear the cache partition in order to regain usability. I'm probably trailing off in the wrong direction though...
I did find this post in the Desire S forum under their Bliss port of a user who stated an app called Swapper really sped things up. HERE is the post.
I haven't done too much research on it but curious if anyone else does?

Autokiller memory optimizer.

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.

[Q] Info on V6 Supercharger script

Is it possible to run this script from galaxy w? I have some ram issues and sometimes my phone lags.
In running services these applications are always open:
Facebook
hotmail
go launcher ex + go launcher notification + go locker
maps
swiftkey
I have read somewhere that this script is not very good with multitasking but it makes the phone run faster and smoother. These applications are considered in multitasking? Or in this case multitasking means for example to have messaging, browser etc running at the same time?
Thanks

Yes u can install v6 script in GW
Ur phone will be faster
But u should search the forum before posting
From My GWonder

Okay thank you!
Sent from my GT-I8150 using xda app-developers app

I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.

piefert said:
I've had some probless with supercharger, when closing apps with stock task manager, launcher would always close, and have to reload all the apps and widgets (stock touchwiz launcher). Can this be solved?
Sent from my bananaphone.
Click to expand...
Click to collapse
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)

I installed Supercharger on my phone and now it works better altough some games runs slower and freezes on my device,

reidzeibel said:
That is called "Launcher Redraw", technically, when you clear memory or run a resource-demanding apps, Launcher will be killed as well to give more memory.
To prevent this, set the "lock home in memory" option in V6Supercharger. Note that doing this will make your home launcher unkillable and thus your free memory will be lower.
My advice: If you do want to lock launcher in memory, use a low memory usage launcher, such as zeam, Go Launcher uses too much memory.
Hope this helps.
Reidzeibel
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!

irishpancake said:
Ehhh??
Lock home in memory is not in V6....actually, if it is enabled in Launcher or ROM, Zepp recommends not to do this!!!
From my memory, you got "Hard to Kill", "Die Hard" or "Bulletproof" depending on OOM and Minfree values you choose in the script....
Obviously, Bulletproof means Launcher will never be killed!!
But, the script expects that "lock home in memory" to be disabled, AFAIK.....if I am wrong, I apologise in advance!!!
BTW, if your not on ICS, can I recommend that old favorite Launcher Pro.....it may lack support from the Dev, but it runs silky smooth on GB and is lightweight with many options!!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)

reidzeibel said:
Yes, Zepp advise not to enable the option IF you don't know what it is used for
Yes, If the launcher or ROM supports "Keep home in memory", do this instead of using supercharger script, I forgot to write this, thanks Irish for adding that part
Sent from my Modded Stock DXLA2 (Didn't have the mood to update)
Click to expand...
Click to collapse
Well, I don't know friend.....
every tutorial I have seen or read including Zepp on the V6 Thread, says you should disable this setting if you have it, as it interferes with how V6 manages memory.....
and if you leave it enabled, it may cause lag on your device, the advice is to disable it, and Compcache [zRam]....If you don't have the option, it don't matter, so it's mainly aimed at CM7/9 ROMs.......
to achieve same result, V6 uses the Bullet Proof Launcher, but I think Zepp now advises to use the HTK option, as BPL breaks some other stuff in ICS.....
just to emphasise, it is important to read the outputs given in the script......
Zepp can be a hard taskmaster if you ask something covered there or in help files, etc.
Small example of his comments here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

//EDIT2:
My original writing here was:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Click to expand...
Click to collapse
These words might have been choosen to sharp for this given thread. See the further discussion for more details.
The essential core of my statement is to use the Supercharger with care, as you might run in more problems than before, if you do not know about your usage scenario and the side effects that come with every change in those parameters.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.

XR-7 said:
Forget the Supercharger. Instead take cear of the number of your apps and their intent-behavior.
Scripts like Supercharger are pure mess when targeting a solid daily driver system.
The number of people using this script is only high because there are a lot of folks with little knowledge about the underlying techniques.
Tweaking settings like those of Supercharger is always a trade-off - but you can only adjust them if you know which flavor of system-behavior you prefer. Most users don't have a clue, so they have to believe magicians - Unlucky for them, because the provided magic potions are not more than nicely advertised placebo.
But at least, they got some great funky banners, so you can easily spread your unawareness in the whole xda forums via your signature through adding them.
// EDIT:
You can optimize memory management for either single task scenarios or multitasking scenarios. Logically, this is a classic trade-off.
To give an simplified example:
- Higher low-memory-killer-borders increase the chances of getting a smoother experience when running only one specific app most the time.
- On the other side, multitasking user experience will suffer, as activities get flushed out of memory earlier, when free memory decreases.
Other example: The VFS Cache Pressure parameter, which controls the weight between file system cache and application memory space.
- Lower values should give you better experience, wenn handling similar task scenarios most of the time, since their access patterns improve through caching
- On the other side, there is less memory space for applications, so this setup will give you slower task switching, as it is more likely now, that your desired new foreground application is not present in memory anymore.
Click to expand...
Click to collapse
Sounds like you've been reading my thread.
Thanks for confirming everything I've said LOL
Fact is, nobody can preach about android memory management and be right without confirming my findings.
So you're right.
And you confirm my findings.
Thanks and you're welcome.
PS. People know they hate launcher redraws and know they like it fixed.
But then again, you haven't read the thread or tried supercharger otherwise you'd know that it has different flavours for multitasking, aggressiveness and balanced.
And it's popular because it's for those that do know, and those that don't - not to mention that it works and does what it says.
If anybody thinks it's a placebo, it's in their head.
And you're wrong when you say "scripts like SuperCharger" because there is no such thing as a script like SuperCharger... silly.
edit: oh about VFS cache pressure, you can check that and all the other placebos in the Kick Ass Kernelizer script.
You fail to mention the importance of min_free_kbytes and dirty ratios and lease-break-time in your attempt to sound knowledgeable.
I guess you were too busy enjoying hearing yourself talk.

Man...
I woz goin to write that....but you just did it for me....
from the horses mouth, so to say!!!
Thanx....
hope you didn't mind the pic.....captures the essence of Zepp
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Code:
Edit:
I withdraw offending remarks about XR.....
as I have no knowledge as to his level of knowledge....
and in all humility I know phuck all myself....
OK??
Peace
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!

irishpancake said:
Duplicate post!!! Sorry
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!
Click to expand...
Click to collapse

irishpancake said:
Man...
EDIT....of course in XR's OP the EDIT bit was missing, so of course be had a quick look at the V6 thread....went Ohh Ohhhh!!!!
Click to expand...
Click to collapse
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
irishpancake said:
Man...
but he is so "knowledgeable" or some kinda know-it-all know-nuttin
Click to expand...
Click to collapse
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.

Just read post 3 in my thread.
It was never a one-liner. (well bulletproof launcher used to be at first)
Lock Home in Memory was a one-liner and it wasn't good enough.
All 3 launcher strengths are stronger than "lock home in memory" and there are 3 strengths precisely because there are trade offs...
Reading the script output would explain it anyway but suffice to say, you have said nothing that contradicts anything that I've said.
And very few users have problems with it and has a very good reputation.
Otherwise, this wouldn't happen:
http://goo.gl/qM6yR+
http://goo.gl/1JPl8+
Of course, that is only counting clicks on the goo.gl links... not all clicks.
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
I've listened to you talk in circles so here's some advice: know what you're talking about before talking about it.

XR-7 said:
Sounds logic. I see that a am completely wrong at the V6-thread, so i go back, place a big EDIT-Label under my text, and add more text, so that every one can cen see it? Not.
Seriously, the examples i gave are there to line up the claim i did in the first part: V6 SuperCharger is no the glory fire-and-forget solution, most of those performance-increases come with some kind of accordant disadvantage. This should be mentioned.
For some kind of stuff, one does not need >500 posts, but a solid technical comprehension, common sense and some research on the web.
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
@zeppelinrox
What i wanted to express is: Those settings are trade-offs concerning the user experience. This stands in contrast to your explanations, which claim to bring both speed and multitasking to every phone. Forcing the home launcher to stay in memory is a good idea, but it was a one-liner until ICS came, so this can't be the reason for running hundreds LOCs at system startup.
The majority of users has a bunch of other problems, with their device configuration messed up, too much resource-intensive apps installed or a bad-performing ROM installed at some time.
And then there comes this shiny tool, it sounds like the good old american way of life (and is named like it): giving resources here, spending some more memory here - there's no limit, it makes your device blazing fast, it gives you all the things you dreamed of, on your old sluggish device.
Naturally, thats not the case: Yes, there might be useful scenarios, as it allows switching beetween LMK-profiles etc. But lets be honest: Normal users have no clue what they are doing there, playing around and getting more problems than before.
Actually, i like your idea of making those parameters accessible with more ease. As a advanced user, you can archive performance gains, because you know what to set for your specific usage scenario.
Its simply not the fire-and-forget-speedup for android, but people tend to believe this.
// Update:
I added a more diplomatic statement to my original post. Although my technical base argumenttion is the same as before, i guess its good for the discussion if there are less misleading emitotional expressions.
Click to expand...
Click to collapse
OK man XR......I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
You can check my posts!!
But, you were being provocative IMHO, and that is usually a good basis for discussion
OK!!
Sent either from my Sammy GT-i8150 or my Momo11 Bird Tablet!!

irishpancake said:
I have removed my offensive comment about you, mainly becoz I don't know you and have no basis for the comment I made, and also becoz I think I cannot stand over it, so accept my apology please....
its not my usual form at all!!
Click to expand...
Click to collapse
That's okay. As i mentioned above, i had also choosen sharp words, guess there might have been some more suitable writing style.
Nevertheless, i also guess that both sides - positive and negative - of the supercharger script should be discussed, as it is definitely note the magic silver bullet as it is sometimes perceived.

zeppelinrox said:
But you get the idea: the sky's the limit.
And yep... it's like getting a brand new phone.
Click to expand...
Click to collapse
Yes, it's remarkable. Not only one's device becomes at least a Galaxy Nexus, but it also increases display size, brigths up your teeth and pleasures your girlfriend.

You should get this for your girlfriend: https://play.google.com/store/apps/...GwsMSwxLDEsImF0dGljbGFiLkRyb2lkVmlicmF0b3IiXQ..
But if her device is SuperCharged, you're out of a job but mostly because you bore everybody to death.

i try v6 for a day, at night i realized that sms that i send in a day just keeping sending without being sent, i've tried to unsupercharged and reboot phone, but sms still sending, until i restore system to earlier setting than restart the phone, and check for the messages are sent
what is wrong with it?
what version of v6 that support stock rom?
is v6 increase free ram or is it does anything else? because i see no different on free ram that showed in ram booster
one more thing, when i run the script, i see text "it will not run on this rom, but you still can cook bla bla bla" is it normal?
Sent from my GT-I8150 using xda app-developers app

[ALL ROMS][HOW-TO]Speed Up & Maintain - [CM-7/9/10/10.1][UPDATED]

I know, many people here want to have Android 4.x.x on their phones, but unfortunately, because of low-end processor as well as less RAM, these CM10/CM10.1 ROMs are laggy and slow. I am also one of them, but, after using these type of roms since 4 months, I have now got a perfect idea of using them. So, I am sharing the way I use these roms. Many people told that this also helps for CM7 users. So, now I have declared this thread as UNIVERSAL PERFORMANCE THREAD. This method can be used on - Stock | CM7/9/10/10.1.
NOTE : This thread is mainly from galaxy mini forums. But, I have posted it here also, so that Gio users also get its benefits.
NOTE : This method is same for PAC ROMS.. because they are based on CM. So, you can use this on PAC ROMs also.
♦ FINDING STABLE VERSION :
First of all, you will need to find a good stable version of any CM7\CM9\CM10\CM10.1 ROM. Find stable version by asking in general discussion thread of those particular ROM and then download that version. But, do not flash now.. Follow next step.
Note : For CM7 users - Official CM7 is best, but if you want you can try it on custom roms also. If you are using CM7 custom or stock based custom rom, then for scripts n tweaks to work, you must delete all the scripts from init.d so that scripts will not get overridden.
♦ SLIMMING THE ROM :
Slimming means making rom size less by removing unwanted and unnecessary applications from system/app. It reduces system memory use. Here is a chart of cm10.1 apps which are safe to remove - LINK
With reference to that chart you should remove following apps with adding alternatives to them.
Note: Left side apps are to be removed and right side apps are alternatives.
● LatinIME.apk - WP7 Keyboard App
● Browser.apk - Holo Web Browser
● CMFileManager.apk - Root Explorer File Manager
● Trebuchet.apk - Holo Launcher
NOTE: On CM7, default ADW is good, but you can also use Holo Launcher.
Other apps that can be removed without alternatives-
● CalendarProvider.apk - One of the big RAM consuming apps. This app start anytime, you do anything, so it will be a big save of memory removing this app. But, you will get problems with calendar sync..
● GoogleCalendarSyncAdapter.apk - Reomove this only if you do not sync calendar.
● Email.apk - If not in use.
● Gmail.apk - If not in use.
● Talk.apk - If not in use.
● GoogleBackupTransport.apk - It is used in google backups, remove on your own risk. (Not a risk, i always remove it.)
● ChromeBookmarkSyncAdapter - No use.
● HTMLViewer.apk - Never needed.
● UserDictionaryProvider.apk - It is useless without LatinIME.apk.
● VisualizationWallpapers.apk - Wallpapers app. Remove it always.
● CMWallpapers - Remove it always.
● VoiceDialer.apk - Do you really use it?
● LiveWallpapers.apk - Dont you care for your battery?
● QuickSearchBox.apk - If you dont use.
● PicoTTS.apk - Text to speech function.
NOTE: Alternative apps should always be installed in system/app only. For that, I recommend you to remove these apps drectly from rom's zip before flashing.
♦ USE OF SCRIPTS N TWEAKS :
Many people use hard scripts n many tweaks to get good performance. But, it is totally wrong.
Highly recommended to use Activo Speeder. It is the best script for performance. Dont use anyother thing with it- such as ram manager, seeder or anyother script.
(Note: If the above script doesnt work on your device then please find another good script and flash it.)
IT IS RECOMMENDED TO USE SUPERCHARGER ON ICS\JB :
After testing a lot, I found that SuperCharger is the best script which can be used with any ROM to get more performance and for perfect RAM Management. Here are some steps on how to use SuperCharger -
● Here is the original thread for SuperCharger script.
● Script can be downloaded from this download page.
● Download latest script as well as starter package if needed (Read Original Thread).
● Now, for 4.x.x ROMs, you do not need to do anything with services.jar. But, for below 4.x.x, services.jar needs to be patched to get SuperCharger Memory Management working.
● Now, copy script to SDcard and run it with Script Manager as root. For more detailed guide plz prefer the original supercharger thread.
● Now, you are running the script. You will find many options and info on screen. Read it all and choose what you want.
NEW DISCOVERY : SUPERCHARGER + CROSSBREEDER = ULTIMATE PERFORMANCE WITH MAX ENTROPY ! - by Dark Passenger
● LINK FOR THE POST.
Here are some tweaks-
In Build.prop -
●
Code:
ro.ril.disable.power.collapse=0
and change the value from 0 to 1. (Add the line with proper value if does not exist)
This one is for battery saving.
●
Code:
dalvik.vm.heapgrowthlimit=48m
If it already exists then just match the values.
This is a VM Heap management for RAM.
●
Code:
ro.ext4fs = 1
Improves EXT4 performance.
● IMP :
Add following lines below "# Other" in build.prop
Code:
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
(If exists, just change the values as above).
(Note: This one will remove location feature increasing performance freeing up more RAM. This frees up to 30mb of RAM)
And now remove NetworkLocation.apk from system/app as well as com.android.location.provider.jar from /system/framework.
For further build.prop tweaking, you can use this great guide -> Click Here. Thanks to Dark Passenger for some build.prop tweaks.
This much tweaking and scripting is enough. DONT USE TOO MUCH TWEAKS N SCRIPTS.
♦ BASIC APPS TO USE :
Your rom's performance also depends on the apps which you use. Always look for apps' memory usage and if the app consumes more ram then try to find an alternative app for it. Here are some basic apps which you should use (i always use them).
● Use Root Explorer as file manager, Holo Launcher as Launcher.
● Use Cache Cleaner App. It is must. Clean cache once a day.
● Use Root Cleaner App. A must have app. Do "Quick Cleaning" twice a day. It will regulate your performance.
You can also freeze the apps you are not using at that time, such as DSPManager (Unfreeze it only at the time of listening songs)
Freezing Google Apps will be a great way to reduce RAM consumption.
● Use this amazing app - Autostarts. This app controls the apps that start automatically in your phone. If you want settings which I use then PM me. I will tell you, how to use this app.
CLICK HERE FOR AUTOSTART APP SETTINGS
● ABOUT TASK KILLERS :
Using task killer is good but, it is also bad. Task killing is actually meaningless. Some apps never really get killed. They start again n again. So, use Autostarts instead task killers. But, here is a nice app for killing processes and freeing RAM. This is the original app. I have themed it to look good. Download it here.
Use it as a task killer, press menu button and include system processes and then start killing processes which are useless.
● Try to use apps as system apps.
● If you are using UC Browser then in its settings, check "Clear Data on Exit". If did, you will see UC will take less than 10mb but, if you wont do this, UC will take more than 15mb.
♦ IMPORTANT TIPS AND SETTINGS :
● Always flash rom with a clean wipe and proper flashing method.
● Do not flash gapps again if they are included in the rom.
● Do not flash internal memory scripts as they reduce performance.
● Use Adrenaline Boost. Boost once or twice a day. Boosting much will increase battery consumption.
● Use Root Cleaner app and freeze the apps which you are not using at that time. Freeze Google Play Store, Google Services Framework and other google apps which are always on. Unfreeze them when you want.
● The apps used for Backup purposes should not be installed always. Keep them in your sdcard and install them when you want and uninstall when done with them.
● Basic apps should always be in system/app.
● In Developer Options -
Set all animations scale to .5x
Set Background Process Limit to "Atmost 4 processes", if issues occur then set it back to "Standard Limit".
Enable "Kill App Back Button". Always use this feature to come out of the apps which do not really exit on pressing just back button.
● Do not expect much from our phone as it is not a high-end phone. Dont expect good battery life but, still to gain good battery life. Keep RAM free by using the ProcessKiller app as told above. I always get 170 mb RAM free.
● Do not charge battery until it gets discharged upto 10% or less. While charging do not remove it till it reaches 100% and 20 mins above that.
● Calibrate battery when needed.
● Avoid use of apps which are always running either in background or foreground.
● Press thanks. .

Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS.
Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!

StiQuezNL said:
Thanks! I'm definetely going to try this out, even though I'm not running JB but ICS. Deleting unneeded apps works on every Android version I think, and ActivoSpeeder works on ICS too, so I'm happy!
Click to expand...
Click to collapse
As I hv mentioned in the title.. this method is for all ROMs.. It is not needed that you should be running JB only.. it is for all...

Noobwithdumbquestions said:
this made everything a lot more laggy and gmail stopped syncing... Also takes about 3 times as long to boot.
No offence, but this is pretty terrible. And after doing some actual research a lot of the "tweaks" you talk about here are never proven effective and frowned upon by actual experts. Even in the article you linked the writer says that something like dalvik heapsize is not something you should or have to change.
I would advice anyone to NOT waste any time on this.
ps: the last part (under tips and settings) is actually some good advice, although the background process limit is not saved in CM10 (and the max.mem tweak doesnt work), so you'll need to do that everytime at startup
Click to expand...
Click to collapse
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1

Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660

tcris45 said:
please dude if you don't know how to tweak you can go i don't use this guide but it's a good one maybe you installed all those thing over a already tweaked rom, this guide if for clean stock, cm7/9/10/10.1
Click to expand...
Click to collapse
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.

Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..

FlemishDroid said:
Nice guide...but I think you are wrong about the services.jar. You have to patch it when you use ICS or Jelly Bean, not on GB. And there is no Official CM7 on Gio.
Verstuurd van mijn GT-S5660
Verstuurd van mijn GT-S5660
Click to expand...
Click to collapse
Yeah services.jar needs to be patched on ics and jellybean only. I didnt knew that official cm7 is not there for gio.. I dont own this device. sorry.

Noobwithdumbquestions said:
I applied it on a clean cm10.1 twice, had the same results, twice. I am not trying to talk down on someone elses work, but the fact is that some of the "tweaks" he talks about are never proven and often based on urban myths and the perception of people who applied them and saw improvement (placebo effect). fwiw, OP himself links to an article that busts some of the myths about tweaks, he tells people to apply...
So, maybe my device didnt start to lag more, in fact, it might have been more stable... however, setting the fs.file-max too big (as is one of the many things that activo script does) will make it less responsive, like there is a 100ms sleep between every action... I also experienced that with manual sysctl.
And some other tweaks that do work are still not great for everyone because they got other side effects that are not mentioned anywhere in this article. I got no idea why sync started giving errors and gmail stopped updating (twice) after these tweaks, but they did....
I am completely new to android, and should've done more research before blindly following some article that states to have some magical cure. But I am not new to linux and it seems this community suffers from the same kind of idiosyncrasies at the bottom end, where people constantly try to fix **** that isnt actually broken.
I'm talking about tweaks here obv, removing gapps. bloatware and lowering requirements for the OS is obv fine...
When someone's Gio lags, it's probably because they want to do stuff with it it's not made for, it's a slow device with minimal specs that does the pure core tasks as pda, phone, messenger and email, and as long as you do those it'll be fine. If you want more, buy a better phone. If it's that important to you and you dont have money, learn to appreciate what is actually important in life.
Nuff said.
Click to expand...
Click to collapse
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.

Dark Passenger said:
okay go step by step and tell me what is it that is actually bothering you about the tweaking.(talk only about supercharger method not activ speedo).
yes most of the tweaks are utter bull**** The tweaks in the op(build prop ones are actually proven read the article again).As for dalvik size its recommended to keep a size around 48 so that you processes don't need to split their dalvik heaps into two separate piles thus reducing ram consumption.
Click to expand...
Click to collapse
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
dalvik.vm.heapgrowthlimit and dalvik.vm.heapsize - BUSTED,
Click to expand...
Click to collapse
This is one property that has cropped up recently in various build.prop recommendations for ICS. Typical suggested values range from “48m” all the way up to “256m”, likely motivated by the common misconception that more is better. The real purpose of this property is much less obvious than one might initially guess. It is also another one you should probably avoid changing.
Click to expand...
Click to collapse
Should you change this setting? Probably not.
Click to expand...
Click to collapse
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
OJ said:
Look in signature, this thread is also there for Fit as well as Mini and is getting good response all over.. but you are the first one to complain on this. My advice to you- DO NOT USE THIS DO NOT POST HERE!
Some of your sayings are correct but, still this is the best way to increase performance. You might have did something wrong because this has been researched by me and some other people that this guide is perfect for low activity devices like ace, fit, mini, but if you dont want to use then dont use. I have NO PROBLEM.(I really dont get money or anything for this). lol..
Click to expand...
Click to collapse
Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...

Noobwithdumbquestions said:
I didnt use the supercharger method... The OP says the activo speedo is recommended, and the supercharger method is proposed as an alternative... I already said what problem I had with it (the response thing, and believe me or not, to me this difference is obvious and makes sense, I was able to reproduce it with just changing some of the same sysctl settings myself) but I wouldnt be surprised if there were more as it seems to do a buttload of things.
As far as the heapsize goes, I am not basing my conclusions on anything other than the OP's own link, which says things like:
Maybe you are right, I dont know all the technical implications, and I got no way to check it other than to test it and I see no difference in ram consumption if I change this property.
The ro.power.dissable thing might shut off wifi when in deep sleep and jumps back to mobile (I think, it happened after applying all tweaks and it seems the most likely thing to do that), but whatever causes that, you should warn people about that sort of thing as it can cost them money..
I didnt use it for long and I'm not an expert, i'm just sharing my findings, people can make up their own mind about it and share their experiences as well..
Click to expand...
Click to collapse
the ro.power.disable.ril actually causes the phones radio to go to sleep so if your mobile data is off there is no reason to switch on rather the wifi might switch off(devs already stated so) and again switch back on once you get out of deep sleep.
its a good thing that you are coming back to provide a feedback and is appreciated(at least should be).
the change for dalvik.vm larger than 48 only allows the heap to grow to that value then split into a new heap since we can't/shouldn't/don't use apps with such a large memory footprint the chances of a split occurring post 48mb(gb and below) and 64mb(ics and above) is highly unlikely hence the changing the value to a larger quantity will make no difference.
PS personally even i dont like activo mainly cause i dont know how it works rather i use supercharger and its a much better option in my opinion.

Sorry, I didnt mean to offend you in any way and appreciate your effort... But telling me to stop posting just because I'm critical seems pretty backwards. If you only want people to say thanks and be greatful all the time, maybe you should start sharing horse pictures on a hello kitty forum...
I'm just sharing my experience and my problems might be related to my rom and it could very well work great on other phones or other roms... But I used a clean cm10.1, the CM10.1 rom almost everyone with a Gio uses, so I'd think it's still important to bring up my findings...
Click to expand...
Click to collapse
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
In fit's thread, Dark Passenger also wanted to express his ideas and wanted to help me. And I was happy about that. Because the way he helped me was like he really wanted to help. But, you was not polite as him.
You can ask Dark Passenger, there is a lot of information in the thread provided by him and I used that. And he never complained like you.
 @Dark Passenger, please explain him.

OJ said:
No, I already told you that many of your ideas are correct but, your way of expressing was not good.
Ex- You said that "Dont waste time on using this guide".
Now, if you think that was correct then please do not post again. If you are providing information then you can but, if you are telling people not to use this then dont post.
Click to expand...
Click to collapse
Yeah, I was frustrated and my first response was not really fair. I agree.

Noobwithdumbquestions said:
Yeah, I was frustrated and my first response was not really fair. I agree.
Click to expand...
Click to collapse
When you use ics or jelly bean you need supercharger script and a patched services.jar (it's easy to do) because any other script don't works 100 % on it.
Sent from my GT-5660 using xda premium

What is eating all the S6 edge memory?

My last phone, the G3, has 3 GB of RAM. The G3 runs Lollipop perfectly. The S6 edge has 3 GB of RAM and there's never any of it. I understand that there's a very aggressive low memory killer but it is ridiculous that a top of the line phone needs to reclaim my podcast app or Audible while they're playing. There should be a ton of free memory and a ton of cached apps in it but the memory is full and there is nothing cached. I've never been so frustrated with a phone. I spend a lot of time sighing at it when it does something stupid. Anyway, if anyone knows where this mysterious memory is being used, please chime in.

There are suspicions that it could be related to the touchwiz launcher, try a different launcher just for the heck of it and see how it goes.
Pp.

gunslingerfry said:
My last phone, the G3, has 3 GB of RAM. The G3 runs Lollipop perfectly. The S6 edge has 3 GB of RAM and there's never any of it. I understand that there's a very aggressive low memory killer but it is ridiculous that a top of the line phone needs to reclaim my podcast app or Audible while they're playing. There should be a ton of free memory and a ton of cached apps in it but the memory is full and there is nothing cached. I've never been so frustrated with a phone. I spend a lot of time sighing at it when it does something stupid. Anyway, if anyone knows where this mysterious memory is being used, please chime in.
Click to expand...
Click to collapse
Hi gunslingerfry,
I was just reading about this on forbes. Here is what their author says to explain the poor memory usage and how to fix it "What should happen is RAM used by apps and services is released when those apps and services are not in use. Instead it is not being released which means each new app or service has to eat into additional memory until there is no more available, at which point the slowdowns and crashes begin.
The only half solutions at present are a) to hit the ‘Close All’ button in the multitasking card menu to dismiss all apps to try and claw some memory back, or b) to reboot the device. Interestingly the latter is expected to have helped keep the issue under the radar in reviews as performance testing is always done from a fresh boot."
So it sounds like you are sort of out of luck for now, but I am sure there will be some update that fixes the issue shortly.

I'm experiencing this myself but apps that I reopen from the multitask window have to reload and I lose where I was previously.. Very annoying to say the least.
Sent from my SM-G925T using Tapatalk

PanchoPlanet said:
There are suspicions that it could be related to the touchwiz launcher, try a different launcher just for the heck of it and see how it goes.
Pp.
Click to expand...
Click to collapse
I never use the TW launcher because I don't enjoy using it. I use Action Launcher. It's very lightweight.
Goldmeyer said:
Hi gunslingerfry,
I was just reading about this on forbes. Here is what their author says to explain the poor memory usage and how to fix it "What should happen is RAM used by apps and services is released when those apps and services are not in use. Instead it is not being released which means each new app or service has to eat into additional memory until there is no more available, at which point the slowdowns and crashes begin.
The only half solutions at present are a) to hit the ‘Close All’ button in the multitasking card menu to dismiss all apps to try and claw some memory back, or b) to reboot the device. Interestingly the latter is expected to have helped keep the issue under the radar in reviews as performance testing is always done from a fresh boot."
So it sounds like you are sort of out of luck for now, but I am sure there will be some update that fixes the issue shortly.
Click to expand...
Click to collapse
Goldmeyer, this doesn't explain why it's 75% utilized on boot but with no running apps (according to the smart manager app). I've tried the build.prop tweaks posted around here and there is a significant difference. Smart manager reports there are dozens of apps being pre-loaded on boot (which is normal, this is what we want!) but with the same 75% utilized. Those tweaks tended to lag the device after a couple hours, which may be a manifestation of what the Forbes article is referring to. So I guess the thing I don't get, and maybe a better understanding of what the dha/lmk values that are being tweaked would help, is what is currently allocating all that excess memory? Is TW just allocating ridiculous amounts of memory to make sure it runs smoothly? Is Android hoarding it for its own uses? And if so, how can any device with less than 3 GB of ram possibly function on Lollipop?
On a much more technical note, I understand that running 64 bit means using a little more ram. Addresses are twice the size and integers will be twice the size but that doesn't explain 2.3 GB. It shouldn't be loading the entire system partition into ram.