Develop Bugs

[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

Multi-tasking woes with AOSP (CM10, AOKP, PA)

This is not meant to be a complaining post, mostly I wanted to see if anyone else is having my problems.
I am currently running ParanoidAndroid 2.50 (CM10 based ROM) and I absolutely love how all AOSP ROMs look and feel. TouchWiz had some neat things, but it felt really bloated.
My problem is, multi-tasking on AOSP blows, really, really, really, BAD. I mean it's downright as bad as HTC One X's Sense UI multitasking. For whatever reason, I can never get my free RAM to dip below the 600 MB limit. Usually it hovers around 750 MB, and occasionally I can get it down to 650 MB.
I am not a huge multitasker, but I HATE HATE HATE app re-draws and reloads. This was the one nice thing about TouchWiz, it would keep my opened applications running until I was absolutely at the bottom of my free RAM (~150 MB). My frequently used applications almost never needed to be reloaded/redrawn. This is especially big for applications like Youtube and Browser/Firefox, as you lose everything that you had loaded otherwise.
I've tried spamming opening apps, and the most apps I seem to be able to have open at once is around 8-10 depending on the circumstances. As soon as I cross that threshold of open apps, my other opened apps start being force closed, and require a redraw/reload. This is an absolutely pitiful amount of apps, especially with the whopping 600-800 MB of free RAM that I usually have.
I also have the issue that sometimes even when I don't open a lot of apps, some of my apps like to force close for no reason after a few minutes of being idle. My MailDroid and Firefox apps seem to be extra susceptible to this random time based force close compared to GoSMS, which rarely closes after an inactive period of time.
I have tried multiple kernels, multiple ROMS, multiple governers and I/O schedulers, and I even tried zeppelinrox's V6 supercharger + multitask mods. Nothing I do seems to allow me to crack into that 600 MB of unused RAM. I am so flustered by this that I'm actually considering going back to TouchWiz.
Could anyone else provide me with some feedback with their multitasking app limits/free RAM? Is this a known CM10 issue?
TL : DR
-I can never get below around 600 MB (usually hovers around 700MB) of free RAM
-My running app limit seems to be 8-10 with about 6 widgets
-My apps seem to force close after short durations of inactivity
-I experienced NONE of these problems on TouchWiz
-Could someone post their numbers for some of these things, and is this a known problem for CM10?

Same problem here... I think most people like this problem though. Many like to see more free ram, but I prefer faster multitasking. My main concern is my downloads being closed and interrupted.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yeah definitely a known issue on AOSP. Memory allocation issues I guess. I've never seen a dev comment on it, despite the fact it has been brought up several times. I suspect we won't get a fix until the JB sources are released for the d2.

Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?

zeppelinrox said:
Post your services.jar
If you used the windows tool to patch it, it may not have worked - I've made quite a few changes for greater compatibility since it's last update.
btw what are your minfree settings?
Did you do the aLogcat test?
Click to expand...
Click to collapse
Oh wow it's zeppelinrox! Hi
Yes, I used the Windows Jellyscream tool to patch my services.jar. The ICS Service Center in your script insists that it worked, but CM10 does not currently have a "Charge Only" or "No Action" mode when the cable is plugged in, I'm forced to mount the SD card(s). Your tool specifically says do not do that, but I don't really have a choice :/
My current MinFree values are:
8, 14, 40, 50, 60, 75
I have also tried the auto-calculated ones (which in my opinion leaves way too much free RAM theoretically):
8, 16, 325, 358, 390, 423
Both of them didn't seem to make a difference.
I have attached my services.jar to this post as well as requested.
As for aLogcat, I'm not sure what that is or how to do that

Hi
Well I can't open it up... is the file size correct?
Maybe it's an incomplete upload.
I assume that it's for ParanoidAndroid 2.50 so try upping it again since I haven't cracked one of those open yet lol
The service centre only looks at the supercharged launcher aspect and the windows exe isn't up to date for the multitasking mods.
I've actually just updated the ultimate jar script today... and also has an SGS3 specific edit
However it may be only for the stock rom.
The aLogcat test is described in the ultimate jar thread OP.

Weird, I'm also not able to open the one on my phone, that's kinda scary.
Ok, I'll give your new ultimate script a spin, and I'll look into the aLogcat thing as well and try to provide you some information.
Here's the services.jar file that was leftover in the Jellyscream directory (JellyScreamPatcherV6_0.9.0.6/framework/services.jar). I chose not to delete the temp files, so I'm guessing it's the same file.

WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?

ChrisG683 said:
WOOOOOOOOOOOOOOOOO!!!!
Wow you were right zeppelinrox, I tried out your Ultimate Jars script and BAM, my phone is hauling ass right now. Down to 234 MB of free RAM and none of my apps have force closed on me at the moment even after running ~20. Also, my list of cached apps is MASSIVE now, my RAM is finally being utilized!!!!
Time will tell if my apps auto-close after inactivity, but damn this is awesome, THANK YOU SO MUCH, you rock .
Hopefully the windows tool gets updated eventually so it's easier for people to do this, it was a bit tedious to figure it out haha xD
Edit:
My only question now is why oh why do the default AOSP settings suck so bad?
Click to expand...
Click to collapse
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752a
am: Allow more hidden apps on devices with lots of RAM
* If more than 1.5GB is present, allow up to 40 hidden apps. * Number is somewhat arbitrary, but was found to work well on D2. * Also look at the sys.mem.max_hidden_apps value if given.
Click to expand...
Click to collapse
Uh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around

zeppelinrox said:
btw how did you decompile?
Click to expand...
Click to collapse
Hmm, I'm not sure what you are asking here, could you clarify?

zeppelinrox said:
I think that's to make me look good
I hope to have it automated somehow like the outdated ics webapp.
btw how did you decompile?
I'll try again when on the PC.
edit: ok that second one you posted opens up fine. I guess that's CM10?
It looks like CyanogenMod is following my lead... https://github.com/CyanogenMod/andr...mmit/9a8117c4f887c8b0df9cadb5d9aa7689a878752aUh yeah... you get a 40 app limit only if you have 1.5GB of RAM - otherwise, you're STILL stuck at 15 hidden apps... lol
I had already seen the "sys.mem.max_hidden_apps" code in ProcessList.smali before the last script update - so that's already been bypassed to 70.
I just didn't know where that setting came from lol
So if you're on CM10, the Ultimate Jar Power Tools script that's currently available already fixes that.
Of course, "sys.mem.max_hidden_apps" was introduced after my mucking around
Click to expand...
Click to collapse
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.

ChrisG683 said:
Hmm, I'm not sure what you are asking here, could you clarify?
Click to expand...
Click to collapse
OH that's ok.
The second file you posted decompiled fine
themadproducer said:
hey zeppelinrox....
And to think, that I read some debates with users downplaying the usefulness of 2gb ram vs 1gb. When I was on my HD2 with Swap/Zram, I was using your script(s)...but at one point, I had OS AutoKilling disabled entirely (can't even remember how I did it) and was using a fairly complex Tasker profile(s) to Kill ALL if my memory ran down to a critical stage....all except apps that I put in an EXCEPTION list. So basically, I had MAX multitasking...and the use of all available memory unless I hit a critical threshold...and then, aside from those apps on the exception list, all other apps would get killed. To this day, I believe that Android should be built with an Exception list for power users similar to your Bullet Proof thing.
My Stock S3 rom and kernel seem to handle things pretty darn well. I use Go Launcher EX and experience zero redraws and my tests so far indicate that the OS has great multitasking behavior. I can open quite a few apps for a good amount of time. Eventually they get killed, but as you know, it's a bit unpredictable. When I last ran the memory down to about 250mb, which was very difficult to do even with large games, the OS hardly killed anything. It wasn't a scientific test but feel factor based. One of these days SOON, I need to play with your scripts again. Only reason I haven't with the s3...is because so far the stock setup is working really well.
Click to expand...
Click to collapse
Yes you were using dorimanx's trick to break the lowmemorykiller on HD2
He asked me to break it on ICS and above, which I did.
But that only lasted a day because I found another way to do it... boost number of running apps without breaking lowmemorykiller.
Needless to say, dorimanx got real happy lol.
See post 2 of the ultimate jar thread for more about that.
So yeah, you still have the app limit and lots of room for more multitasking since you can't get very low on ram.
I've added more mods to reduce the likelihood of apps closing on you. (Check the change log)
Sense users are ecstatic with the latest
Anyway, I'm sure that if you try it, you'll notice a difference - it's just a matter of you not knowing how much better it can be

What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Deoxlar said:
What program are you using to put on the app kill exception list?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Deoxlar...are you asking me?
With the HD2, I had the OS rigged to NOT kill any apps EVER and used System Tuner Pro as my APP Killer with exceptions checked off. I used Tasker to determine the ram availability each time a window opened or changed, and Tasker would trigger STP when necessary.
But Zepplinrocks' V6 Supercharger as a very unique system for doing similar...but overall, it handles everything to do with ram management and better. Also, for some people's setup, it is a dramatic improvement...a FIX... a LIFE SAVER. (Basically the rom Devs are going to eventually slowly STEAL Zeps ideas. But we will not forget.
My old HD2 memory mngt system was an ALL or NOTHING workaround so it suffered in that regard.. The way my S3 with stock ICS is handling things right now is surprisingly good. I did a test last night opening as many apps as possible until I basically ran out of FREE ram. At that point, the OS was doing it's thing, killing another app or 2 so it could run the new app launched. Multitasking...or switching to newly launched apps and then returning to previously launched apps where they left off....worked near flawless and FAST on my i747m. When I woke up today, 3/4 of the apps were still in memory ready for resuming.
This is why I went from 2 years of OBSESSIVE flashing and tweaking....to using my new S3 with the Stock rom and about 1/100th of the tweaks. Super STABLE and not a slouch. I hope the upgrade to JB...well....is an UPGRADE. yadda yadda yadda...:good:

Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
{
"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"
}
The 16th hidden app gets killed because the limit is usually 15.

zeppelinrox said:
Hey, for shi.tz n giggles do that aLogcat test that I describe in the multitasking OP... I'd be interested to see what your max hidden app limit is
Install aLogcat, run as many apps as you can, run aLogcat and search for longer.
Most people get this before the mod...
The 16th hidden app gets killed because the limit is usually 15.
Click to expand...
Click to collapse
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".

themadproducer said:
For you Zep, I do about any test you asked me to do! Respect! :good:
Stay tuned....possible depression, followed by possible "V6...light at the end of the tunnel".
Click to expand...
Click to collapse
LOL thanks for the kind words man

zeppelinrox said:
LOL thanks for the kind words man
Click to expand...
Click to collapse
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.

So, you're using the "ultimate jars" script in conjunction with which ROM? And did you use in conjunction with the supercharger script?
Just trying to understand exactly what is required to "fix" the multitasking issue.

themadproducer said:
OK, I used System Tuner Pro's log and guess what....checked a dozen times....
hidden #51
Yup...and also using "free" in STP terminal, I have 115mb free close to 1.6gb used.
I cross referenced by reopening the apps and most of them were still in ram memory.
Actually, a few games I was testing almost 20hrs ago, were still in ram. That surprised me.
So these games/apps were not killed off by idle time auto killing.
This is why I haven't tried any CM or custom roms. This thing seems to be doing way better...then the forums would lead me to believe. I was FLASH happy with my HD2 and never quite satisfied but this thing is so much better...and mostly stock.
What do you think Zep...honestly, have you heard any similar reports?
UPDATE: now i am down to 83mb free...still rock solid smooth.
Click to expand...
Click to collapse
Wow I've never heard of a stock rom having the app limit set to 50.
However when you type free in terminal, how much is system tuner reporting as free?
There is a difference because the free command in terminal is always very low whereas apps like system tuner/task managers always report free ram as "free ram + cached apps" which is a much bigger number.
Can you post a deodexed services.jar (it's probably odex tho since it's a stock rom) or at least the smali files?
The windows patcher should be able to decompile it.
If it's not sense I'd only have to look at ActivityManagerService.smali and ProcessList.smali.

[SHARE] Battery Saving Techniques!

NOTE: Im turning this into a sharing thread where everybody can post and share their techniques on how they save battery consumption. I'll quote all the useful suggestions here in the first post
I would like to start off by saying that all ROMs basically consume badly just like the stock version. There could be little to no differences between them with regards to battery performance. Right now I would like to share my observation, on what I presume to be one of the best ways to save battery while maintaining good performance.
glennlevi's Technique:
1. Get Antutu Battery Saver Pro (Free version can be found in the market). Install and untick the option control cpu speed.
2. Using No Frills CPU, or any other built-in cpu settings app, select your default governor (bcm####) and sio as your I/O scheduler. Maximum Frequency should be your highest available, and Minimum Frequency your lowest available.
3. Manually adjust screen brightness in settings to about 20%.
4. Untick Background Data and Auto Sync in settings, under Accounts and Sync Settings.
5. Get Ram Booster (Free in market) and install. Open. Under settings, set Boost Level to aggresive, set whitelist apps and tick your launcher, sms app, keyboard, and Ram Booster and Antutu Battery Saver. Untick Show Overlay Widget in Overlay Widget Settings. Enable the widget in the notification bar, refresh every 5s, Report Style Dont Show. Under Advanced Settings, set Feedback to None. Clean Ram using this app everytime just before you turn off your screen or want to stop using your phone.
6. Drag down your notification bar and tap the Ram Booster Notification. Now wait a couple of mins while browsing through your phone (without opening any apps)
*You can use other task killers if you want, but Ram Booster is the best IMO. A better replacement however is 360 launcher's cleaner widget (which will save more memory, ram and battery usage since its all in one app)
7. Open settings and go to Applications>Running Processes and look at all running apps, you will see some auto-start apps like Beats Audio, DSP Manager, Google Mail, Google Maps, Google Playstore and others. Uninstall all user apps that have autostarted. Download Titanium Backup and use it to uninstall stock bloatware, like google maps and google mail, or other custom bloatware like Beats Audio (If you dont use them at all). Clean Dalvik Cache using Titanium Backup and Clean Cache using Ram Booster. Freeze seldom used apps like Google Playstore. Just unfreeze when you want to use them.
*You can use other apps like Root Uninstaller to remove system apps, but IMO Titanium Backup is the easiest to use and has one of the most functions.
Click to expand...
Click to collapse
Imacatlover's tips:
Imacatlover said:
The best way to save battery is really to know your fone.
1. any type of widget should be avoided( except maybe clock) as they are juice hoggers.
2. ANY app that suggest or implies that they save battery defeats their own purpose for they themselves consume battery life...figures.
3. ANY app that has "killer" attached to it isn't really helpful because most of the app be it user or system just restarts after. Same goes for anything with "booster"..
4. Ram cleaner should suffice
5. keep most settings to a minimum.
6. Accept the fact that our little fone has one crappy battery construction..
Click to expand...
Click to collapse
irfanbagus' tips
irfanbagus said:
i do. well, not full kernel, just kernel module. search bacem-tweak in dev section. but i find that the best thing you can do to save battery is keep your phone sleep as long as possible. that's means remove bloatware, limit installed app with service, and only turn data/wifi when needed. combine with undervoltage, usually i got 3-4 days in single charge. in some very rare condition i got 6-7 days.
Click to expand...
Click to collapse
There you go! Have a blazing fast and battery healthy SGY!

i'll try that as soon as i can

OxygeenHD said:
i'll try that as soon as i can
Click to expand...
Click to collapse
Just to be clear, using Titanium Backup and changing CPU settings requires a rooted phone
Well, most custom roms are rooted anyways. Im just saying this cuz you might be running on stock rom

Nice tutorial :good: :good: :good:

Good one thanks mate xD

I'd like to confirm a few things. some of info on this thread is never heard.
glennlevi said:
2. Using No Frills CPU, or any other built-in cpu settings app, select your default governor (bcm####) and sio as your I/O scheduler. Maximum Frequency should be your highest available, and Minimum Frequency your lowest available.
Click to expand...
Click to collapse
bcm work almost like performance gov. are sure about it?
5. Get Ram Booster (Free in market) and install. Open. Under settings, set Boost Level to aggresive, set whitelist apps and tick your launcher, sms app, keyboard, and Ram Booster and Antutu Battery Saver. Untick Show Overlay Widget in Overlay Widget Settings. Enable the widget in the notification bar, refresh every 5s, Report Style Dont Show. Under Advanced Settings, set Feedback to None. Clean Ram using this app everytime just before you turn off your screen or want to stop using your phone.
Click to expand...
Click to collapse
is this information have been confirmed? as far as I know fewer widget is low ram consuming and more battery friendly. notification will prevent your device sleep. notification for every 5 second?it will make your battery life decreased, a lot. on other hand, clean ram have been proved consume huge battery power.
6. Drag down your notification bar and tap the Ram Booster Notification. Now wait a couple of mins while browsing through your phone (without opening any apps)
*You can use other task killers if you want, but Ram Booster is the best IMO. A better replacement however is 360 launcher's cleaner widget (which will save more memory, ram and battery usage since its all in one app)
Click to expand...
Click to collapse
why should I use it when android have it's own task killer.?
7. Open settings and go to Applications>Running Processes and look at all running apps, you will see some auto-start apps like Beats Audio, DSP Manager, Google Mail, Google Maps, Google Playstore and others. Uninstall all user apps that have autostarted. Download Titanium Backup and use it to uninstall stock bloatware, like google maps and google mail, or other custom bloatware like Beats Audio (If you dont use them at all). Clean Dalvik Cache using Titanium Backup and Clean Cache using Ram Booster. Freeze seldom used apps like Google Playstore. Just unfreeze when you want to use them.
*You can use other apps like Root Uninstaller to remove system apps, but IMO Titanium Backup is the easiest to use and has one of the most functions.
There you go! Have a blazing fast and battery healthy SGY!
Click to expand...
Click to collapse
most android app work with autostart. in fact, all you can see in android is actually an app. debloatware is a good recommendation, but a complete app removing? please make sure about the validity of these information.

NEED THIS ONLY
By

kurotsugi said:
I'd like to confirm a few things. some of info on this thread is never heard. bcm work almost like performance gov. are sure about it?
is this information have been confirmed? as far as I know fewer widget is low ram consuming and more battery friendly. notification will prevent your device sleep. notification for every 5 second?it will make your battery life decreased, a lot. on other hand, clean ram have been proved consume huge battery power.
why should I use it when android have it's own task killer.?
most android app work with autostart. in fact, all you can see in android is actually an app. debloatware is a good recommendation, but a complete app removing? please make sure about the validity of these information.
Click to expand...
Click to collapse
First off I would like to quote myself -
"Right now I would like to share my observation, on what I presume to be one of the best ways to save battery while maintaining good performance."
As such, Im sharing this because
1. I think it might help other people.
2. I've tried it and compared it many times in many different rom, and what I recommend is based from my own experience
3. I know youre a dev. Im not, obviously. That doesnt mean I cant share what I think is useful. This is also backed up by the fact that Im not claiming Im sure that these actually work and that I can back it up with additional information. Again, this is just based on my experience.
again I would like to repeat the quotation from myself:
"Right now I would like to share my observation, on what I presume to be one of the best ways to save battery while maintaining good performance."
There you go. I hope that clears it all up. So please dont pick on me or anything just because Im not a dev. Thank you.

nope...I never intended to pick on you. I'm just feeding up my curiosity. I'm sorry if you feel like that.

thanks for sharing we need tat support...other be frank..be opened for sharing..
Sent from my GT-N7000 using xda app-developers app

kurotsugi said:
nope...I never intended to pick on you. I'm just feeding up my curiosity. I'm sorry if you feel like that.
Click to expand...
Click to collapse
Well, thanks anyways for noticing my thread. Now I know some of my suggestions may be far from the theoretical facts that you know, but there are times when actually testing something and comparing it with others yield better results than just looking up the figures. Thats just my take on it though, so Im not saying thats all there is to it.
Anyway, maybe I'll edit this thread and make it a SHARING THREAD instead. I'll just regularly view it and put all suggestions that other members have in the first post

glennlevi said:
Well, thanks anyways for noticing my thread. Now I know some of my suggestions may be far from the theoretical facts that you know, but there are times when actually testing something and comparing it with others yield better results than just looking up the figures. Thats just my take on it though, so Im not saying thats all there is to it.
Anyway, maybe I'll edit this thread and make it a SHARING THREAD instead. I'll just regularly view it and put all suggestions that other members have in the first post
Click to expand...
Click to collapse
The best way to save battery is really to know your fone.
1. any type of widget should be avoided( except maybe clock) as they are juice hoggers.
2. ANY app that suggest or implies that they save battery defeats their own purpose for they themselves consume battery life...figures.
3. ANY app that has "killer" attached to it isn't really helpful because most of the app be it user or system just restarts after. Same goes for anything with "booster"..
4. Ram cleaner should suffice
5. keep most settings to a minimum.
6. Accept the fact that our little fone has one crappy battery construction..

good tutorial
I will try it
Thanks

Imacatlover said:
3. ANY app that has "killer" attached to it isn't really helpful because most of the app be it user or system just restarts after. Same goes for anything with "booster"..
4. Ram cleaner should suffice
Click to expand...
Click to collapse
do you ever wonder how ram cleaner works ? by killing some applications. ram cleaner = task killer.
6. Accept the fact that our little fone has one crappy battery construction..
Click to expand...
Click to collapse
not that crap if you realize it's 2011 android phone with $120 price. right now with that money you can find a lot better phone, but in late of 2011 there is only few choice on that price range.

Please share your battery saving techniques and tips here! I will add the good ones on the first post with quotation.
Probably when there are already a lot, I will compile all tips to make one big guide which has been contributed by the whole community. Lets work together on this

irfanbagus said:
do you ever wonder how ram cleaner works ? by killing some applications. ram cleaner = task killer.
not that crap if you realize it's 2011 android phone with $120 price. right now with that money you can find a lot better phone, but in late of 2011 there is only few choice on that price range.
Click to expand...
Click to collapse
hmm... seems legit
Cant argue with you on that, most apps are generally glorified task managers, there are a few good ones though.
That's why i'm planning to buy a new android this christmas, maybe S1 or S2 depending on my budget.

wonder why no one want to make a battery saver kernel than superspeed kernel...

Imacatlover said:
That's why i'm planning to buy a new android this christmas, maybe S1 or S2 depending on my budget.
Click to expand...
Click to collapse
why not nexus phone ?
i do have plan to buy another android phone after i give my sgy to my girlfriend and back to my old rokr e6. but not this year. too much spending money for gadget this year.
encik_racun said:
wonder why no one want to make a battery saver kernel than superspeed kernel...
Click to expand...
Click to collapse
i do. well, not full kernel, just kernel module. search bacem-tweak in dev section. but i find that the best thing you can do to save battery is keep your phone sleep as long as possible. that's means remove bloatware, limit installed app with service, and only turn data/wifi when needed. combine with undervoltage, usually i got 3-4 days in single charge. in some very rare condition i got 6-7 days.

irfanbagus said:
why not nexus phone ?
i do have plan to buy another android phone after i give my sgy to my girlfriend and back to my old rokr e6. but not this year. too much spending .
Click to expand...
Click to collapse
Sir i want to ask you onething, offtopic, in nexus there is no memorycard slot, so we have to keep all data including gallery files and even a new rom in phone memory. If we want to flash a new rom, then how can we do that? While we wipe the data and cache before flashing all data will be deleted? The rom file too?.
Sent from my GT-S5360 using xda premium

I am using juice defender, i think it's good.
Sent from my GT-S5360 using xda premium

[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

Random Builds and Development

Hi all.
This thread is for random builds and development. There is no agenda other than to keep the Kindle Fire alive for the few of us that remain. This thread is not meant to support any specific ROM. I hope this is okay with the forum administrators.
With that said, please join in. We're all in this together.

Cm-12.1 2015-10-15
I made a public viewable folder on my Google Drive for Android stuff here https://drive.google.com/folderview?id=0B7BjC3Ky49TVcjdZQlpHYV9JWXc&usp=sharing
I uploaded a build of CM-12.1. The file name is weird so I will explain (in case you care):
cm-12.1-20151015-UNOFFICIAL-kad-rsm-O3-mo3-wifi-otterx.zip:
kad = kernel compiled with ArchiDroid toolchain
rsm = ROM compiled with SaberMod toolchain
O3 = almost all compiled with -O3
mo3 = more optimization, specifically as much of JustArchi's compiler flags as would work. The '3' is my third attempt to add more optimizations.
wifi = hack to make wifi work without doing a clean install, that is, there is a script, fix-mac.sh, which I think only gets run with a clean install. My hack was simply to copy the file that the wifi driver wants to the name that it wants. This should allow either dirty or clean flashing.
Suggestions:
* Change the animation duration levels in Developer Options to 0.3x or less.
* Use the Noop I/O scheduler for regular things like reading a book (that's why you bought a kindle, right) or browsing the web.
* Use the Deadline I/O scheduler for interactive things like playing a game.
* If you like Gapps, I suggest OpenGapps or TK Gapps. I have not tried this ROM with Gapps.
* You will need to get a third party program to change kernel settings. I like Kernel Adiutor.
The issues:
* Don't use the brightness slider in quicksettings. If you do use it, the status bar goes away and leaves the top part of the quicksettings panel in its place. I suggest disabling the slider and using the brightness control in the status bar settings. I'm not sure if this is a new bug or the result of too much optimization.
* There are no app snapshots in the recents switcher. This may be internal to Android as a way to save memory for low RAM devices, or it may be a bug in CM.
* The Kindle Fire just doesn't have enough RAM (or rather Android is just too freakishly bloated). Attempting to run memory intensive apps will likely result in them crashing or running slowly because the RAM they are using is being swapped to ZRAM. You may be able to adjust the ZRAM size and get better results.
There you have it. I hope you find it useful.

Ah. I just realize this thread. Going to try the 12.1 now
Sent from my Nexus 5 using Tapatalk

@pfederighi. Running fine and fast on the first boot. I clean flashed it without gapps.
After I flash Pico opengapps, it's rather slow now, but probably adjusting things. I'm going to use this for a while and see.
I M using privacy guard to block wake up and keep wake permission for (almost) all apps, since I don't use app that need to do that. Been set it up like that since ur cm11. Gave me very good battery life.
Will post some screenshot later
Thanks for this
Sent from my Nexus 5 using Tapatalk

Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
{
"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"
}
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk

Battery life looks good.
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
View attachment 3514625View attachment 3514626View attachment 3514627
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.

Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?

kev716 said:
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
Click to expand...
Click to collapse
U don't need supersu. There's su app built in. Try installing Adiutor again, I remember I had that issue too, but I re open it, and it ask superuser request.
Su setting is on developer options. It's enabled by default.
Did u open kernel Adiutor and supersu from notification panel? (the one that tell us that xxx app is installed). I did, and it give that error. starting the app from home screen and app drawer works fine. Dunno if it's related to notification panel one, or u just need to open it twice.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
pfederighi said:
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Click to expand...
Click to collapse
I don't use that many app, so dunno have experience with crashing. I use 1gb zram since ur cm11, although I don't see any benefit. No crashes though.
I'll try 256mb later then.
I thought swap is remmended at 2x ram on Linux?
Sent from my Nexus 5 using Tapatalk

dokie80 said:
I thought swap is remmended at 2x ram on Linux?
Click to expand...
Click to collapse
Indeed, but that is swap to disk. ZRAM is the method of allocating an area of RAM that is treated as a compressed disk and using it as a swap file system. It is a way of using limited RAM more efficiently, at the expense of CPU time, but it is still using RAM. So, on our device, 100 MB is eaten up by graphics buffers and proprietary firmware. Another ~300 MB is eaten up by Lollipop itself. This leaves us with ~100 MB for user programs, which is not a lot. If you allocate ZRAM at 60 MB, that leaves 40 MB of regular RAM + ~120 MB compressed on the ZRAM drive for programs. This gives us more memory to work with, but effectively 75% of it is compressed, which means every time it's read, it needs to be decompressed, and every time it's written, it needs to be compressed. The memory manager of linux does a great job of making it efficient, but it still slows down the system.
If Android were to actually swap to disk, which it can do, it would wear out the solid state media very quickly because there are a limited number of writes before the media no longer works. There have been great advances in the field of solid state technology such as Intel's and Micron's new 3D XPoint (it's awesome, check it out). So, in the near future this may no longer be an issue, but it doesn't help our old devices.
If you really do need the memory, you can make a swap file on an externally powered USB hard disk, mount the drive, and then issue a `swapon path_to_your_swap_file` from the terminal. I've done it before. It's painfully slow, but it works.

Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Regarding not using ZRAM:
From what I understand, yes, if you have enough RAM without using ZRAM, then it's generally better to not use it.
Regarding KSM:
KSM compares the specified number (default 100) of RAM pages per check. If it finds that any RAM pages are identical, it merges them to a single copy-on-write page (that is, they will remain merged until a process attempts to write to it, at which point it'll be copied back to separate pages). Since there are often many read-only pages that happen to be identical, it tends to be very effective.
It runs at the specified interval (default 500ms). I've found that increasing the interval to 750ms or even 1000ms significantly reduces system load with no appreciable difference in the amount of RAM freed.
Because for some CPU & RAM intensive programs I've noticed slightly worse performance with KSM running, I have sometimes run KSM for a few seconds to free up the RAM, disabled it, and then run said program. It seems to work rather well. I suppose I could also have left it running and just increased the sleep interval to a higher amount, say 10000ms.
In general, KSM will free up about 10% of the total RAM, which in my experience is true.

CM-11.0
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.

Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.

pfederighi said:
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Click to expand...
Click to collapse
I would be interested in a 10.2 build.
And of course thx for all your interest in keeping this device alive. Great little tablet.

pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I don't remember facing those issues. About have to press button several time to wake up, sometimes it just need 1-3 secs for the screen to wake, probably because of low cpu clock too.
I remember using 10.x that has privacy guard, but it's different from 11.x. As long I can block wake up and keep wake, I'm sold.
As the sound,
Anyway, since you re offering otterx version, I definitely will test it out, since it's easy and won't require a pc.
Thanks
Sent from my Nexus 5 using Tapatalk

pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I thought CM11 had more free ram than CM10?

VTCruzer said:
I thought CM11 had more free ram than CM10?
Click to expand...
Click to collapse
10 is faster, much more responsive than 11. For free RAM I'm not sure, but AFAIK, free RAM can be set using minfree. More free RAM doesn't mean it will run faster, it just mean less crash on apps and more capable on running apps that need high ram.
@pfederighi already explain about the zram. Using that, we can get more free RAM, but will use More cpu to decompress the zram when accessed. So, probably not faster than without using zram.
If we really want to compare the ram, I suggest to compare the usage (system), not the free one.
Sent from my Nexus 5 using Tapatalk

I too would be very interested in a 10.2 build for otterx