Develop Bugs

Solution to low memory issues and lag?

EDIT: These settings don't seem to be read by the lowmemorykiller process, so they have no effect. But the app Autokiller modifies the settings in /sys/module/lowmemorykiller/parameters/minfree and that one works!
Hey guys, I just noticed this thread and it's very interesting.
http://forum.xda-developers.com/showthread.php?t=622666
Android has its own low memory task killer, and it can be configured. I checked the defaults for my JPC Froyo firmware, and it was set a bit low, meaning processes are not killed as soon as they should be.
I also think I've found a new way to configure those options:
I modified my /system/build.prop file and added the following lines.
# tune the lowmemorykiller
ro.FOREGROUND_APP_MEM=5120
ro.VISIBLE_APP_MEM=8192
ro.SECONDARY_SERVER_MEM=12288
ro.BACKUP_APP_MEM=12288
ro.HOME_APP_MEM=12288
ro.HIDDEN_APP_MEM=20480
ro.CONTENT_PROVIDER_MEM=22528
ro.EMPTY_APP_MEM=24576
Reboot for it to take effect.
These values are twice my original ones. You can check current values by doing a "getprop".
NOTE that these values are in PAGES (4K). So 24567 pages = 98,304 KBytes.
Strangely the /sys/module/lowmemorykiller/parameters/minfree values are not changed. But I think the lowmemorykiller might be reading the prop values directly. I'm running many programs now trying to hit the limit and see if it takes effect.
EDIT: It seems to be working! I can run many many apps and the phone remains responsive. Unused apps are killed as needed. Check out the screenshots below:

Is this Froyo specific or does it also apply to Eclair?
Edit: Never mind

Isn't this pretty old news?
Aren't there are apps in the Market for this (AutoKiller, MinFreeMgr)?
I guess if you know precisely the best settings for your own phone, putting them in a startup script makes sense. I didn't realize build.prop could be used to set things like that.

distortedloop said:
Isn't this pretty old news?
Aren't there are apps in the Market for this (AutoKiller, MinFreeMgr)?
I guess if you know precisely the best settings for your own phone, putting them in a startup script makes sense. I didn't realize build.prop could be used to set things like that.
Click to expand...
Click to collapse
MinFreeMgr tries to do the same thing but by editing a different file which doesn't stay on reboot. This build.prop edit is a new finding, and it seems to work. I think it could be a better solution as it stays after a reboot. The difference between this and other Auto Task Killers is that this is using Android's built-in memory management mechanism which is much smarter than any external task killer can be.
So far it works really well!

Can we convert this into a workable program?

Very interesting, will give it try.

hardcore said:
MinFreeMgr tries to do the same thing but by editing a different file which doesn't stay on reboot. This build.prop edit is a new finding, and it seems to work. I think it could be a better solution as it stays after a reboot. The difference between this and other Auto Task Killers is that this is using Android's built-in memory management mechanism which is much smarter than any external task killer can be.
So far it works really well!
Click to expand...
Click to collapse
Yeah, I acknowledged the build.prop was interesting, very interesting, actually. I wonder if you could set other parameters in there that some of the modders are throwing into init scripts and/or small apps.
For clarification, the two Market-available apps I mentioned (AutoKiller, MinFreeMgr), both do the exact same thing you're talking about. AutoKiller is poorly named, as it's not a task killer per se, it merely modifies on the fly the settings you're talking about here; same with MinFreeMgr. Both can be set to take affect at startup/reboot. Advantage, can be changed on the fly without reboot, disadvantage, another app to load during reboot.
Thanks.

distortedloop said:
For clarification, the two Market-available apps I mentioned (AutoKiller, MinFreeMgr), both do the exact same thing you're talking about. AutoKiller is poorly named, as it's not a task killer per se, it merely modifies on the fly the settings you're talking about here; same with MinFreeMgr. Both can be set to take affect at startup/reboot. Advantage, can be changed on the fly without reboot, disadvantage, another app to load during reboot.
Click to expand...
Click to collapse
Ah, thanks for clarifying that. I discovered those values when I did a getprop. The values I posted above (2x default) work okay. But now I'm trying slightly less aggressive values (1.5x) to see what might be the optimum - too much free RAM is also a waste.

By the way, what task manager is that your pics are of? Looks like the Samsung Task Manager, except the RAM tab. On mine, that tab's Summary and does not give the same info as yours. Mine's unchanged on the various firmwares I have used JG1, JG5, JM1, JM5, JM6, JH1, JM7...

distortedloop said:
By the way, what task manager is that your pics are of? Looks like the Samsung Task Manager, except the RAM tab. On mine, that tab's Summary and does not give the same info as yours. Mine's unchanged on the various firmwares I have used JG1, JG5, JM1, JM5, JM6, JH1, JM7...
Click to expand...
Click to collapse
You're right. Its the JPC Task Manager. It has those extra options to clear the memory. I don't use them now though.

With Eclair I have 326MB ram. Froyo has less just 304.
And after we speak for galaxy lag. I thing it is an android lag because the system to start cut ram from frozen apps and to give at the new application they try to open, the free ram must be 48mb.
Very less for the UI.
I am not happy. We let WM so as to don't need fixes and custom rom. And we have other problems.

I will give it a try. Already modified my build.prop and un-installed Autokiller. Will check for the next few days.
P/S: Probably due to placebo effect, but it feels more responsive.
If it works, this is a good hack!

distortedloop said:
By the way, what task manager is that your pics are of? Looks like the Samsung Task Manager, except the RAM tab. On mine, that tab's Summary and does not give the same info as yours. Mine's unchanged on the various firmwares I have used JG1, JG5, JM1, JM5, JM6, JH1, JM7...
Click to expand...
Click to collapse
That's the froyo task manager, which can be found in the earlier froyo (xxjp3) release as well.
If you want, i can attach this apk (either odexed or deodex, you pick) for you to try on eclair.

hardcore said:
Hey guys, I just noticed this thread and it's very interesting.
http://forum.xda-developers.com/showthread.php?t=622666
Android has its own low memory task killer, and it can be configured. I checked the defaults for my JPC Froyo firmware, and it was set a bit low, meaning processes are not killed as soon as they should be.
I also think I've found a new way to configure those options:
I modified my build.prop file and added the following lines.
# tune the lowmemorykiller
ro.FOREGROUND_APP_MEM=5120
ro.VISIBLE_APP_MEM=8192
ro.SECONDARY_SERVER_MEM=12288
ro.BACKUP_APP_MEM=12288
ro.HOME_APP_MEM=12288
ro.HIDDEN_APP_MEM=20480
ro.CONTENT_PROVIDER_MEM=22528
ro.EMPTY_APP_MEM=24576
Click to expand...
Click to collapse
Hey, I was thinking about this, and I started to do some research and found that for Froyo, other devices are using these as parameters:
ro.FOREGROUND_APP_MEM 1536
ro.VISIBLE_APP_MEM 2048
ro.SECONDARY_SERVER_MEM 4096
ro.BACKUP_APP_MEM 4096
ro.HOME_APP_MEM 1536
ro.HIDDEN_APP_MEM 5120
ro.CONTENT_PROVIDER_MEM 8192
ro.EMPTY_APP_MEM 10240
I'm just wondering if we should be increasing the memory sizes or decreasing them?? Maybe do a combination of both?? I gotta do more research, find out how each attribute behaves, and get more info before editing this stuff.

YG007 said:
Hey, I was thinking about this, and I started to do some research and found that for Froyo, other devices are using these as parameters:
ro.FOREGROUND_APP_MEM 1536
ro.VISIBLE_APP_MEM 2048
ro.SECONDARY_SERVER_MEM 4096
ro.BACKUP_APP_MEM 4096
ro.HOME_APP_MEM 1536
ro.HIDDEN_APP_MEM 5120
ro.CONTENT_PROVIDER_MEM 8192
ro.EMPTY_APP_MEM 10240
I'm just wondering if we should be increasing the memory sizes or decreasing them?? Maybe do a combination of both?? I gotta do more research, find out how each attribute behaves, and get more info before editing this stuff.
Click to expand...
Click to collapse
I think increasing is better if you want apps to be auto killed. The default values (for JPC at least) are half of what I suggested. And it didn't seem to be aggressive enough for the SGS.

hardcore said:
I think increasing is better if you want apps to be auto killed. The default values (for JPC at least) are half of what I suggested. And it didn't seem to be aggressive enough for the SGS.
Click to expand...
Click to collapse
Just a side topic, saw your CSC is OLBJG4, did you manage to flash and got it configured automatically, or that *#272*HHMM# still does not work, and you have to set the apn manually?

hardcore said:
But now I'm trying slightly less aggressive values (1.5x) to see what might be the optimum - too much free RAM is also a waste.
Click to expand...
Click to collapse
That's the mantra in linux "free memory is wasted memory."
I first saw this stuff discussed here. Probably nothing you haven't figured out yet.
I think the settings for any individual are going to vary; there is no set answer, too much of variable in how you use your phone and what apps you use, etc.
You might check out "AutoKiller", it's free, and has some presets, along with ability to roll your own settings. I'd play with it until I found the numbers I liked best, then you could bake them into your build.prop. That would save you the slight hassle of editing and rebooting.
You can also just echo them from the terminal app, but I'm sure you already knew that.
But for those who don't, here's a sample from the above linked article:
Code:
su
echo "1536,2048,4096,5120,15360,23040" > /sys/module/lowmemorykiller/parameters/minfree
Also, while you're playing with settings, have you also looked at changing the i/o scheduler. Lots of debate over what's best. Again, I think it just depends on how you as an individual use your phone...

g00ndu said:
Just a side topic, saw your CSC is OLBJG4, did you manage to flash and got it configured automatically, or that *#272*HHMM# still does not work, and you have to set the apn manually?
Click to expand...
Click to collapse
I sortof hacked it into my /system folder manually. Just need to replace some files there. Auto APN does work. Maybe I'll write up a procedure when I'm more sure of it.

Interesting. Keep up the good work!

hmm...what is the difference between setting it in build.prop vs setting it in autokiller?

[[Speed Improvements]] Brainstorming & Testing Thread!!

Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets​
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2​
Difficulty Easy - Controlling app 'net Access​
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3​
Difficulty Moderate - SD cache/readahead tweaking​
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4​
Difficulty Moderate - Overclocking​
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5​
Difficulty Advanced - How Android Manages Memory/apps​
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6​
Difficulty Advanced - Managing Apps that auto-start on boot​
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any BLAC-specific tweaks that others should be made aware of!

Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).

ThaiDai said:
Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).
Click to expand...
Click to collapse
I'm sure there are more as well... These are just the ones that I found made the most difference on my device.
I'm also curious about the minfree setting. I've only tried a few settings, they seem good. I haven't done any drastic number changing, it seems like changing these values should be done with a lot of caution and testing. There are definitely some values that should not be touched and others that can take some more fudging with numbers .

Added Topic 3 and Topic 4 to startup.txt and rootfs.img.
Just booting. Let's see if this is stable.
Software options I do not test now because I only test the new versions now. So specific app optimization only necessary when ThaiDai Android Loader and installation procedure reaches v2
Ok, boot ok, started Android (NeoFROYO build(, will tell tomorrow if stable.
If so I will use this options as standard for Blacky and I will add software like Droid firewall.
Thanks and good night

Update - I redid topic 4, feel free to re-read it.

Thanks
Enviado desde mi FROYO BLUE CWM1.9 usando Tapatalk

Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?

john_matrix said:
Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?
Click to expand...
Click to collapse
No clue. What does that have to do with the Speed Improvements thread?
I'm guessing you tried and it didn't work? What APK!?!
I guess I don't really follow your train of thought. Does sqshfs'ing and odexing an APK make it run faster...? I'm pretty new to Android in general. Never even used a native Android device .

http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630

farukb said:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630
Click to expand...
Click to collapse
I still don't get what that has to do with our builds. ODEX and DEODEX have nothing to do with our builds... That stuff only applies to native devices, or builds that are ported from native devices (I would think).
Perhaps I'm missing something here... please tell me if I am .

Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.

ThaiDai said:
Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.
Click to expand...
Click to collapse
LOL!
Epic.

OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it

x12CHRIS18x said:
OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it
Click to expand...
Click to collapse
Did you make the choices in the script, or did you just exit the script?
You have to make sure ScriptManager is running as root too. There's a setting for it. "Browse as root" - make sure that is enabled. You won't be able to see /data without browsing as root.
...You have a TouchHD? I always thought you had a RHOD, lol.

>> A super easy way to improve One X Multitasking significantly (rooted phone only)

>> A super easy way to improve One X Multitasking significantly (rooted phone only)
Guys, there are some discussion on different post indicated One X Multitasking is not as good as previous HTC phones. Sometimes you can only have very few APPs in background, and sometimes you switch APPs and find it has to reload or not return to the place where you were.
Here is a method I have tried which is significantly improve the Multitasking for One X. It only worked for rooted phone, so if you are not rooted, no need to try below action. It will not work.
1. Go to Google Player store to download and install APP "System Tuner" (it is free)
2. Run System Tuner. In its main screen push "Active Tweaks" (right besides the CPU button)
3. In the new windows, up right press Auto-kill tweaks. It will bring another screen show all the value indicate the lowest memory to trigger auto-kill by system default during out-of-memory for each group. (you do not need to care what does it means if you not know it). You'd better to make a screen shot to save these value. So if you do not like the change below you can modify to the default value.
4. There are two buttons at the bottom of screen, press the bottom left button, then in pop windows choose the second choice which I think is good enough for One X. I do not see the need you manually change the value for each group and try to figure out that is the best, just choose from list provided is enough).
After that you will see all the 6 figures has changed to 4M, 8M,10M,16M,24M,32M. And it is done. Now you can try to see how good Multitasking is on your One X.
You do not need to keep System Tuner APP alive, after the action above it has change some files in system and it will mostly kept there. These change make the auto-killer not so strictly like before. Of course if you reboot the phone those setting will change back to default. And you can do those action again. And you can use the bottom right button setting to make it works after even reboot but I do not want to go into detail for that.(not to change make it works after the reboot make it easy for you to change back to default value just by re-boot the phone).
Some notes: you do not need to read below at all if you not interested in)
- System Tuner is a very powerful tool can do lots of thing. I would not recommend you use it for other modification of the system unless you know what you are doing.
- Some simple explanation of the display info's meaning for action 3 above -
Android puts each running app into 1 of 6 Out Of Memory(OOM) groups based on their priority. They are FOREGROUND_APP, VISIBLE_APP, SECONDARY_SERVER, HIDDEN_APP, CONTENT_PROVIDER, and EMPTY_APP. The value after each group is the amount of memory limits trigger OOM condition that will start kill APP. The lowest group (EMPTY_APP) get killed first.
For my One X EMPTY_APP is set to 80M as default. And if you click right white icon on that screen it will show what APPs under each group. Actually most APPs you have will be in EMPTY_APP group which being killed first.
- Since some guy reported that latest ROM update make multitask better, so probably HTC has changed the value for each group to small limit. If you can give screen shot and tell which ROM version you are on we can verify that. Or you can just report the value for EMPTY_APP. (mine is 80 and not upgrade to latest rom yet)
I hope it will helps those who suffered from bad multitask performance of One X. Enjoy and thanks the author of "System Tuner"

Thanks for the great easy to follow post will respond and let you know any improvements.

The OOM values don't help much with the situation as the phone has plenty of memory for our applications. This can be demonstrated by checking the list of running applications in Task Manager. Notice how fast it takes to start up the application but it takes a second or two to reload the information in it? Many of the programs that will have to reload are loaded into the memory. The problem is the way HTC has set the system to deal with the caches of each program (Caches or something else, I'm no Android programmer so bear with me.). HTC has made the One X aggressively kill that cache in order to stop a program from possibly running in the background in order to drain battery life. So if there is a setting that deals with that, that's what I would be looking to tweak.

This phone sounds have lot of memory but actually not.
Not let the theory to prevent you trying the method. It works great on my one X.

mmx6688 said:
This phone sounds have lot of memory but actually not.
Not let the theory to prevent you trying the method. It works great on my one X.
Click to expand...
Click to collapse
I have tried the method. There isn't a perceivable difference. The issue isn't memory available, but of how the phone manages saved states.

dosen't work, what we need is something that can just terminate the process that phone is using to kill all processes, just wondering about other devices on ICS, do they behave same or its just HTC.

"PROJECT:PLACEBO" - For E4GT Optimization

This article is about the Android Script.
For other uses, please search Placebo; Disambiguation
Op under construction,
Should become read-able soon.
Placebo 3.0 is here! Failed, 3.0.1 may work. lmao
View attachment Placebo3.0.1.zip
Placebo3.0.1-Dropbox
Placebo3.0.1-AmazonCloud
Now supports hotplug governor !
Now makes it's own tweak directory to cut down on overhead !
Now screenstate + CPU1_ON is working better than ever !
Now generates a list of kernel default settings for governors !
SHOULD now flash onto other phones without issue !
DOWNLOAD NOW AFTER READING MORE HERE
The setup I've been using lately uses two scripts; one script that has all of the tweaks and settings, and one small script for screenstate awareness.
Here are some details about installation and use.
1) Download the zip package you intend to install.
2) Boot into recovery with your preferred method. ( I personally just type "reboot recovery" into terminal. I hate holding the buttons...)
3) Navigate to the zip you downloaded and install it.
4) Assuming all went correctly, you will have the quickest flash you've seen, with the least "blahblahblah" possible.
This is normal.
TO VERIFY: Try switching gears. Open terminal emulator and type one of the following.
( you must first type "su" and hit enter )
ondemand
peqasus
conservative
interactive
smartass
lulzactive
If it installed correctly then this will effectively switch you to another governor with optimized settings.
Enjoy.
If this didn't switch you to a new governor, chances are there was a permission or mount failure on my part.
I will be posting additional tools to assist with this part, plus I'm getting a little better at preventing these issues.
To fix it yourself, try setting a governor after typing the following into terminal emulator. (these can be copy pasted if exact)
If it isn't working due to mount; the terminal emulator solution is
busybox mount -o remount,rw rootfs /
busybox mount -o remount,rw `busybox realpath /dev/block/platform/dw_mmc/by-name/FACTORYFS` /system
If if it was a permission related failure; the terminal emulator solution is
for i in ondemand conservative pegasus lulzactive interactive smartass;do
chmod 0755 /system/xbin/$i; done
If you have a problem that neither of these fix feel free to ask me or anyone else in this thread.
Latest scripts
Please read HERE before installing Beta3.1 (technically this NOT Placebo 3 )
PlaceboBeta3.1
Placebo(HEXEN)
(1-10-13 reposted with a couple minor issues fixed)
PegasusQ and dual cpu screenstate plus an SQL settings script
Here's a temp link to placebo2.0
http://db.tt/rsb7tAmY
Here's a sort of greatest hits type of link.
There isn't really any info on them ecxept buried in the thread but I tested to make sure they were all stable
http://db.tt/5KTUtews
A special thanks to:
Hakcenter:
This guy is extremely knowledgeable; willing to help improve others' understanding; has helped me on several occasions (although makes fun in the process ) despite my noobish questions, lack of attention span, and general stubbornness when I'm told I can't do something.... despite us meeting by me posting "Why is thread in the development section" in his apps thread LMAO (sorry, man...)..
For those of you who aren't familiar with Hakcenter, he has an application that applies tweak packages. I liked it when I gave it a lot. I changed some values... but that's not the point! TRY HIS APP. thanks...
Placebo Regulars; Dude, you guys... You guys are absolutely awesome. I honestly think that this is one of the most helpful (as in users helping other users) threads I've seen anywhere on XDA.
Zeppelinrox; His V6SuperCharger was my initial inspiration and his KickAssKernelizer was my initial template... way before Placebo was born.
Calkulin - Im sure I would know nothing if not for your easy to understand scripts having piqued my interest in the first place..
Thank you, sir.
(used nothing directly, but without his contributions....you get the picture..)
TDunham; Always friendly, always helpful, always has good and practical ideas.. never (publicly) judges me too harshly for my lack of ADHD medication...
Can't thank you enough for your kindness... but I can try.
Thank you, sir.
FreeCharlesManson; Your spit-balling and insight led me to a few realizations that altered the effectiveness of Placebo exponentially.
Thank you, sir.
Scarmon; also always helpful and friendly... and makes (at least one that I know of) badass roms that I would recommend to anybody (that I like..).
Thank you, sir.
BlackCanopy...
Two of the most willing-to-help people that I have the pleasure of knowing.. I can't thank you guys enough for keeping this place together.
MiguelHogue....
Team (all of them...) Seriously I still don't know why we aren't all on Teamusxdaguys.... Can't think of anybody in any crew that hasn't been helpful at one time or another.
A word for the wise.. Watch out for that Lickarock... sharp as a tack that one is.. as soon as he buckles down and puts to practice the knowledge slash resources that he already has..
I expect good things will come of it.
Problems?
I've got far more than 99 of em... IO aint one.
j/k
hit me up.... yue noe eye luuuhh yue.
Remember!
If you help one, you have helped us all.
+Good day, sirs+
+ENJOY Placebo+

Repos
..The Pharm..
Welcome. This is a repository with a few of the Placebo1 formats.
Be careful with them, I cannot guarantee them to be universal.
Obviously, of they say Univ then there have no reports of From specific issues. Similarly, if they say TW, don't bother trying on an AOSP build.
Here are some new items for your tool chests...
Format 12 & 7 and a persistent busybox
\\________//
Enjoy
Placebo-Black
Heres a little more info
http://forum.xda-developers.com/showthread.php?p=30348571
"This IS THE DROID you're looking for!!" Come to the black side...
Placebo Black was written on and for
BLACK ROM,
by Team Rejects!! AND Team Nocturnal!!
Works on every rom its been tested on, including JB builds.
PlaceboCmX-1
Placebo Pi. Nice and balanced build.
Nice and balanced. 8/09/12
Placeboπ
DietPill revision 1 (a big hit, simple, effective)
DietPillR1
DietWifiHERE
Placebo-FHV: 8/5 (balance)
http://db.tt/wFL0qtJy
So smooth.... that...
I should call it Santana or Thomas.. Eeer something
http://db.tt/XE2DWzst
Placebo set to Ondemand (performance)
PlaceboOnDmnd
Sugar Pill was an earlier one that was very well received. Stable, simple, gets work done, son!
Crazy Pill was around the same time as Sugar Pill. Can't remember much, except I think I was still adding transitions animations.
There's your warning.
View attachment dietpill-FHI.zip
View attachment SugarPill.zip
View attachment PlaceboFGXVII.zip
View attachment PlaceboFGXXII.zip
View attachment CrazyPill.zip
View attachment PlaceboFGXXVI.zip
View attachment PlaceboFGXX.zip
View attachment ServicesOptAOSKCMP9.zip
View attachment ServicesOptTouchWiz.zip
Check out my new JB compatible Odex Station
#
# RECOMMENDED: PHAKE_SETTINGS
#
dalvik.vm.heapstartsize=12m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=192m
ril.hsxpa=2
ril.gprsclass=['dc 10 mul 4 sub 10';]
ril.hsdpa.category=['dc 8 mul 4 sub 8']
ril.hsupa.category=6\2
windowsmgr.max_events_per_sec=< >
debug.gr.swapinterval=0
RLIMIT_NICE 1
HOME_APP_ADJ -5
HOME_APP_MEM 5688
VISIBLE_APP_ADJ 1
VISIBLE_APP_MEM 11366
#
#

Thank you, you have clearly put allot of time into this... Im gonna check this out.
Sent from my SPH-D710 using xda premium

lolwut

Thank you ! 1st page.

What other scripts have you tested with this master piece?...Is it known to bump heads with any other scripts?
Sent from my SPH-D710

Placebo; Defined
A good reference for governors, definitions of their settings, extweaks, io schedulers, and a whole lot of other things.. can be found
Here, and thank OP of this thread if you like their info
Frequent Questions
My head hurts???
Click to expand...
Click to collapse
So, wait,... what does it do?
Click to expand...
Click to collapse
Here's a little info I prepared about the virtual memory aspect.. this is not complete.. and it's my half assed interpretation...
-------------------Virtual Memory------------------
dirty_background_ratio (threshold at which background data becomes 'dirtyable'
dirty_ratio (threshold at which data becomes 'dirtyable'
dirty_expire_centisecs (time, in hundredths of seconds, before dirty data expires
dirty_writeback_centisecs (time, in hundredths of seconds, before old data is allowed to be written by PDflush Daemons ( a value of ZERO disables flush, out of fear I haven't tried this.
drop_caches (self explained, but the values are | 1=PageCache; 2=InodeCache; 3=both
highmem_is_dirtyable (I don't fully understand this, but my take is it can prevent random/unnecessary I/O within known/mapped files
laptop_mode (determines the time, in seconds, between "disk" I/O and a flush of all dirty data
lowmem_reserve_ratio (ratio of total pages-to-free-pages for each memory zone
min_free_kbytes (this number is used to compute a pages_min value for each lowmem zone
How do I know which configuration is right for me???
Click to expand...
Click to collapse
- Well, that's the real point... you actually have to get your hands dirty here. No way around it.
Is it safe to flash this on ONEROM that is identical to ANOTHEROM?
Click to expand...
Click to collapse
Which one is the best one
Click to expand...
Click to collapse
Well,,, let's start from when you were 3. Go over in detail every decision you've ever made so I can graph what you will like best.

Have no idea how to use this but clearly you put in a lot of effort and it shows (look at the Quadrant! ). Thank you for your contribution and I believe this should go in the Development Section aswell

Lol i have no idea what im doing.. I unzipped it and put it in system bin folder n tried to run it in term emu and got log error so created a log in data log and it did something and log is full of garble but i know im doing it wrong. It was worth a try wish i had some instruction so i could get those scores! Mines under 3000
Sent from my SPH-D710 using XDA

Wish I could figure out how to use this lol, thanks for you hard work! :good:

Placebo:
It's hard to summarize Placebo quickly and in an easy to understand way.
Placebo is a script, or set of scripts, that changes Linux kernel settings in your Android.
It is hard to stay caught up, because the number of potential combinations is almost without limit,
and placebo is constantly changing as I learn/dabble with new/existing modifications.
Some will be for better battery (though all will probably help a little), some will be to make your phone
scream louder than Jenna J.
I would be more than willing to provide more technical information to anybody that requests it.
It's almost pointless to post specific values that are set, as no two Placebos make every adjustment the same,
but there are some constants, for example:
Every Placebo implements a sysctl.conf (or equiv.) which will adjust (at least some of) the following settings:
(The following is a brief breakdown of tunable virtual memory settings, as I understand them.
I do not claim to know a lot about Linux. If you notice something that I have misunderstood,
Please correct me. Flaming will not be responded to. Helpful knowledge will be appreciated.)
-------------------Virtual Memory------------------
dirty_background_ratio (threshold at which background data becomes 'dirtyable'
dirty_ratio (threshold at which data becomes 'dirtyable'
dirty_expire_centisecs (time, in hundredths of seconds, before dirty data expires
dirty_writeback_centisecs (time, in hundredths of seconds, before old data is allowed to be written by PDflush Daemons ( a value of ZERO disables flush, out of fear I haven't tried this.
drop_caches (self explained, but the values are | 1=PageCache; 2=InodeCache; 3=both
highmem_is_dirtyable (I don't fully understand this, but my take is it can prevent random/unnecessary I/O within known/mapped files
laptop_mode (determines the time, in seconds, between "disk" I/O and a flush of all dirty data
lowmem_reserve_ratio (ratio of total pages-to-free-pages for each memory zone
min_free_kbytes (this number is used to compute a pages_min value for each lowmem zone

PhAkEer said:
Honestly I dont see why you would have a problem trying a term.
Is your phone rooted? What commands did you attempt and what was the log output that it returned?
Curiosity; what Rom/kernel are you are using?
Click to expand...
Click to collapse
Not sure what to type lol and what to show you in the log but i am rooted on the universe rom with agats kernel.. I just typed in placebo. It has a ton of info in the log.. Also the universe does have kobridge tweaks which i see it in the logs lol
Sent from my SPH-D710 using XDA

Re: [TWEAK] placebo [$ETTINGS]
Just pm a copy of the log if yoy can... Im at work but will take a look.

Alright, I had hoped to wait until page 3..page 3 is always a safe place... Oh well....
This is a config Im currently working on. If it plays out well, its a big boost in a couple departments.
I cant very well get this thing universal with only one test phone...
Placebo: SugarPill
http://db.tt/in7LAmRN
This one almost effects the battery as much as a new ROM. It will probably take a short cycle before it balances itself out.
These settings are a little aggresive, but Im still taking it easy because I dont want anyone to break anything...
Come on guys, I thought we could all evolve this together =)
FREEBIE:
Ever gone into the supplicant scan's config file? Its pretty useful if you were to... say... Idk... Change the interface to uwbr0.
Your welcome.
(pictures unrelated to above tip)
Sent from my SPH-D710 using xda premium

Much better on the OP. Are you able to provide the download link to the file using the regular xda method (I added one below)? It is easier to see the link and it provides 2 very useful things: it has a built-in download counter (views) and you can remove or update it to new file(s) whenever you like.
Edit: Please put a brief note on the OP with what this script is known to work with (ROMs). And also do yourself a favor and put a disclaimer that you do not plan to support all the roms that are out at this time, try at your own risk stuff. That will save you a lot of headache there are so many different roms out there.

Is there a reason you're leaving /system writable?
Also, this seems to effectively replace kobridge's 41tweaks script, but doesn't address his ondemand scheduler, or build.prop or wifi sleep tweaks. Is that accurate? Can you see any potential conflicts if I kept those?

b1g.p0ppa said:
Is there a reason you're leaving /system writable?
Also, this seems to effectively replace kobridge's 41tweaks script, but doesn't address his ondemand scheduler, or build.prop or wifi sleep tweaks. Is that accurate? Can you see any potential conflicts if I kept those?
Click to expand...
Click to collapse
Actually it was by design to leave those alone, and since I have no scheduler in Placebo, no conflict there. (I smaaawt sah ntine) .
I didnt ask kobridge for permission to insert his work into placebo, so WifiSleepWait is left alone.
If you look for the "*tweaks" youll see what it is.. placebo will interact only with things having "tweak" in their name in its current config.
And about system, thats just a preference of mine. Feel free to add anything (including unmount) to it.
@ Tdun,
Forgive my XDA noobiness, but no actually, I dont know how to make that little tab. Lol
Thanks for all of your constructive criticism/advice. Its much appreciated.
(lol typos when noob=nofun)

Anyway this will work on GB?
Im on Calk's el29 and would love to see if this works on it.

PhAkEer said:
Actually it was by design to leave those alone, and since I have no scheduler in Placebo, no conflict there. (I smaaawt sah ntine) .
I didnt ask kobridge for permission to insert his work into placebo, so WifiSleepWait is left alone.
If you look for the "*tweaks" youll see what it is.. placebo will interact only with things having "tweak" in their name in its current config.
And about system, thats just a preference of mine. Feel free to add anything (including unmount) to it.
@ Tdun,
Forgive my XDA noobiness, but no actually, I dont know how to make that little tab. Lol
Thanks for all of your constructive criticism/advice. Its much appreciated.
(lol typos when noob=nofun)
Click to expand...
Click to collapse
Awesome! So awesome it inspired me to edit my sig. Here's how I'm incorporating your script into my rig:
Code:
echo "SugarPilling"
test -f /system/etc/init.d/41tweaks_kobridge && rm /system/etc/init.d/41tweaks_kobridge
cp /sdcard/gscript/SugarPill /system/etc/init.d/41SugarPill && chmod 755 /system/etc/init.d/41SugarPill
---------- Post added at 03:11 PM ---------- Previous post was at 03:10 PM ----------
apatcas said:
Anyway this will work on GB?
Im on Calk's el29 and would love to see if this works on it.
Click to expand...
Click to collapse
Sure it would. If nothing else, run it interactively and check the log. (I'm pretty sure) the tweaks get reset back to default when you reboot.

lol Im scatter-brained and trying to get out the door for work,
As for GB, I dont see why there would be any issues. I havent tried it, but these are the same things that were in scripts long before I was playing witb them so Id guess that its safe.
Sent from my SPH-D710 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