Database Info

[REF][SCRIPTS] Android Optimization Tips + i9000 specifics (UPDATED 1/10/12)

Attention!
If you're looking for scripts, here it is:
[CWM][SCRIPTS][TWEAKS] Thunderbolt!
Script Reviews are here:
Script Reviews
Introduction
I've been meaning to share this with the whole Android community. It seems unfair that only the i9000 folks have access to the vast research that I've done so far. Hence I'm sharing this in the general Android thread in hopes that it'll benefit everyone in the long run
A lot of people often asked about how Android really works and the optimizations can be made to their Android to make it perform better in terms of:
- battery life
- raw performance
- GUI smoothness
With Android based on Linux, and with the experience I have with Linux/Unix (I deal with Unix/Linux on a daily basis for my work) I managed to find some tweaks that we can do to optimize our phones.
I also hope that people will experiment with the tweaks posted here and feedback to me if there are certain ways that I'm doing incorrectly or there are better ways than what I've posted here.
Script tweaks
There are a lot of scripts in XDA that specifically uses the optimizations (Linux or Android based) that I will explain below to actually increase performance/battery life. However, you need to know what those scripts do before using it.
I've done some reviews of the script here:
Script Reviews by Pikachu01
There are good scripts that are properly tested and made sure that it works. It's a script by Zacharias maladroit, the kernel dev who makes the platypus kernel for CM7 and snail kernel for i9000. I modded it to be compatible with i9000 and it'll probably do more than some of the scripts I reviewed
From there, I've also taken the liberty of modifying it some more based on my knowledge and research I've done. It's called ThunderBolt!:
LINK
Now onwards to what actually goes on beneath the hood.
Android Governors
Some custom kernels provide customized governors for you to choose. These are currently known:
- Ondemand (CPU scales to the highest frequency immediately after a certain CPU threshold)
- Conservative (CPU scales to the highest or 1 scale lower than that after a certain threshold gradually and scales down if CPU is below a certain threshold
- OndemandX (Has sleep codes that scales down the CPU when device is asleep. Threshold is set to scale slower)
OndemandX
OndemandX has a suspend frequency that it maintains when the phone is sleeping. It does have a known issue of waking up too slowly when a call comes in.
Conservative
Conservative is used when you would like the CPU to scale to the maximum through each frequency slowly before reaching the maximum. It saves more battery at the expense of smoothness. There are a few tunables that can be configured in Conservative governor, namely the freq_step and both the up and down thresholds.
freq_step is a tunable that determines how much frequency (a percentage of the maximum frequency of your device) to increase at each sampling rate. e.g. you have 5 as freq_step and your maximum frequency is 1GHz. At each sampling rate, it'll increase by 50MHz. If your current frequency is 100MHz, it'll increase to 150MHz at the next sampling. What if your device doesn't support 150MHz? This is done by splitting time between 100MHz and 200MHz (assuming your next frequency is 200MHz) so that in average, your phone is performing at 150MHz.
The up_threshold is how much threshold to wait for before increasing the base frequency to the next freq_step. I.e. if it is 80, the CPU will wait until it is 80% loaded before increasing the frequency. The down threshold is the opposite of up_threshold, which is the threshold to wait until the CPU downscales the frequency to the next frequency step.
Ondemand
Ondemand is a governor that basically a simpler version of conservative. One difference is that it scales to the maximum frequency after load has exceeded a threshold. This is usually 80. After that, it looks at the load again when it's at the max frequency. If it's below 80 (example), it'll scale down one frequency step. The frequency step mentioned here is the available frequency step. I.e. if your device has frequencies of 100,200,400,800 to 1GHz then it'll scale down from 1GHZ to 800, 400 then 200 and 100.
One optimization I have for Ondemand for i9000 TalonDev is that I tuned it to be 80 rather than 65. I have not felt any slowdowns from using this setting and it saves a tiny bit more battery. You can experiment on this value however you want, but bear in mind that I'm not responsible for any slowdowns or damage that is caused by it. Read up a bit more on thresholds to know more (Google it).
I/O scheduler tweaks
Another tweak that can be done is the I/O scheduler tweak. Some kernels come with a few standard I/O schedulers while others have extra schedulers that you can choose from. I'll explain the few that I know and if you have more information on the schedulers, you can post it here for everyone to discuss/share
CFQ - Completely fair. Most will come with this, but this is not optimized for android. Some kernels do optimize it and use it.
Noop - Simple and least overhead of all I/O schedulers. Produces the best outcome for some cases and some do swear by it. It's downside is that it is easily bogged down by high I/O transactions.
Deadline - Optimized for mobile-like devices like Android. Also, some do swear by this. If its writes_starve sysfs is tweaked to be fair, it's the same as SIO.
SIO - It's a fair deadline scheduler. It's the best scheduler. Nuff said.
VR - A newer I/O scheduler that places penalty on reverse seeks. Not for flash drives, though the R penalty can be tweaked to be a multiplier of 1. Even if this is done, it has a high overhead.. Read more here: http://www.gelato.unsw.edu.au/IA64wiki/IOScheduling/VRscheduler
BFQ - Too high of an overhead, it is optimized for spindle disks.
You can pick and choose from Voltage Control or other UV/OC apps and apply it immediately to feel the difference.
Here's my assessment of all the schedulers that I know:
SIO> NOOP> Deadline > VR > BFQ > CFQ
NOOP is a simple I/O scheduler without overhead that tries to do each I/O transaction as it comes (FIFO). When a group of transactions is detected, it will try to merge it together to make batches of transactions (makes the whole transaction faster). NOOP doesn't have starvation detection, hence if an I/O transaction takes a painfully long amount of time, it will still continue to do it rather than switch the CPU into doing something else e.g. GUI interrupts (i.e. scrolling lists, flicking screens). All other schedulers also have the "merge" feature. NOOP is the only one that makes the "merge" feature its only feature.
CFQ is a complex I/O scheduler that tries to determine the address space of the transaction and applies a cost algorithm in that if the address is close together, it will group them up and perform them. It also tries to make the transaction incremental (i.e. reading/writing through address incrementally so that the disk spindle needs to wind down the least in conventional platter hard disks) The problem is, our flash devices have very little delta between reading a far reaching address space (than the one currently being written/read) or a closer one as it doesn't rely on spindle/rotations. Hence, having this costing algorithm adds overhead and slows down the overall transaction. CFQ has a lot of algorithms to make sure each process gets a fair slice of time on I/O transcations. Too much overhead.
Deadline has a starvation detector and is simple enough that it doesn't have all the overhead of doing rotational/costing disks algorithm. However, reads are done 2x more likely than writes as it has a algorithm based on weights in that reads must be done first if both a read and a write is detected. It has a 2:1 ratio of read to write weights coded into the scheduler (that can be tweaked - writes_starved, will include it in the next version of system_tweak). Hence it's not a fair scheduler.
SIO is Simple I/O that tries to implement a NOOP type scheduler that has starvation detection. Hence, long I/O transactions will be preempted and given CPU time only after other faster transactions are completed, guaranteeing smoothness. Also, it doesn't have overhead of calculating costs. Also, it has a fair number of writes to read, guaranteeing that all transactions are equal.
BFQ has a lot of algorithms to make sure each process gets a fair slice of bandwidth (Budget Fair Queueing). Too much overhead.
V(R) tries to make sure that each transaction has a weight associated with it, being R. And if the seek is reversed, the R will be multiplied by a penalty making it less likely to be processed. Not for flash drives as reverse seek in a flash drive is just as fast as a forward seek.
In benchmarking tests, the tests normally consists of testing the time it takes for a contiguous I/O transfer from 1 point to another. NOOP excels at that because it won't let itself get interrupted to perform another I/O task. This would mean that in real life testing, NOOP will let a long arduous task to finish while at the expense of UI functionality (you will get UI lags)
SIO on the other hand will perform badly at benchmarking as it gets pre-empted when the contiguous tasks takes more than 0.5secs (for synchronous tasks as benchmarking tools perform a synchronous I/O task from one point to another) to another more important task like UI interrupt (when you're scrolling) or Kernel interrupt (when your kernel needs to perform garbage collecting or swap memory etc)
The 0.5 secs can be tuned in the SIO tuneables though, but I would think 0.5 secs for synchronous tasks and 5 secs for async tasks is pretty good to maintain a balance between long/short tasks enabling a smoother experience in Android.
LowMemoryKiller
The LowMemoryKiller is a constant debate between more free RAM and more multitasking capabilities as free RAM (more than 60MB free) is actually wasted RAM. The fact is SGS only has a puny amount of RAM left after a few big chunks are allocated to the Graphics, Modem, Sound and Video (and some others that I do not know a lot about). With that knowledge, Samsung decided to give the SGS SL a bigger amount of RAM when they released it ( about ~650MB of RAM read that from somewhere, can't remember).
The LowMemoryKiller is actually a feature in the Android OS for better memory management.
You can read about it more here:
http://forum.xda-developers.com/showpost.php?p=5442369&postcount=1
This is an important feature due to the perennial problem of having low free memory causing lagginess and slowness in launching apps. When you have free memory lingering around the number of 40MB or less, the Android OS just lags like hell.
What this would mean is, you would want to tweak the LMK to not have the situation of it having less than 40MB (or even close to that).
The modern Linux machine in the Android ecosystem relies on a mechanism called Low Memory Killer (LMK) to consistently free up RAM. This is due to Android's internal mechanism of caching apps (and never fully exiting them) when you press the back button. This is to enable faster app switching and provide a seamless experience for apps usage model. Android also, by itself will also constantly look for often used apps to cache them for faster app opening. This will happen even before your system fully boots.
Now, when you mention LMK, the most obvious thoughts that come up are minfrees and Out Of Memory (OOM) groupings. Yes, those two are integral parts when it comes to LMK. The issue here is that no one actually mentioned that there are two LMK systems in Android, that being:
- Linux LMK
- Android Dalvik VM LMK
Both are separate entities that kills/removes app/dalvik cache from RAM when RAM reaches a certain level.
What confuses most people (including me) is that the OOM groupings of both mechanisms have the same names being (Android 2.3 based):
LMK App Categories
FOREGROUND_APP: Your apps in the foreground, being used currently, interfacing with the user.
VISIBLE_APP: Visible app that is still viewable by the user, but not interacting with the user, example could be apps that reside in the status bar, and giving live information i.e. Os monitor graphs.
PERCEPTIBLE_APP: App that the user can still perceive i.e. Music app that is playing music.
HEAVY_WEIGHT_APP: RAM heavy apps that are not being interacted with, but will be a pain to load if its information is cleared in the memory.
SECONDARY_SERVER: App that acts as a secondary server. Not sure what this really means, but client-server thingy but secondary? Could be something that syncs with an app, but is not syncing currently?
BACKUP_APP: App that is currently making a backup (like Titanium backup?)
HOME_APP: Your launcher.
HIDDEN_APP: An exited app that still significant residual memory in the RAM. Exited only some time ago, or is constantly used by the user.
EMPTY_APP: An exited app that only has small remnants of residual memory in RAM. App that is exited quite some time ago.
Take note that this is my understanding of the OOM groupings. If there are mistakes, please correct me
Tuning LMK
Both the LMK and Dalvik VM has this groupings and they can be tunable by using prop and lowmemorykiller/parameters/adj respectively.
One errata about this is that the Dalvik LMK has one extra tunable which is CONTENT_PROVIDER, which affects widgets that are not currently refreshing or displaying information. The ADJ (which I will explain later) is not available to be tuned though. And it is clearly missing from the Linux LMK.
The ADJ is the so-called priority of the app categories, with 0 being the highest (should not be killed) and 15 being the lowest (should be the first to be killed). I haven't seen values other than 0-15 but I have a feeling that the numbers are arbitrary, and can be extended up to 65535, but who would want to do that since they're only 9 app categories
LMK are specified by pages, with memory = 4 * pages.
e.g.
4096 pages represents 16MB RAM (16 *1.024)
From the Linux LMK source code, the parameters can be adjusted as such:
Code:
* For example, write "0,8" to /sys/module/lowmemorykiller/parameters/adj and
* "1024,4096" to /sys/module/lowmemorykiller/parameters/minfree to kill processes
* with a oom_adj value of 8 or higher when the free memory drops below 4096 pages
* and kill processes with a oom_adj value of 0 or higher when the free memory
* drops below 1024 pages.
Take note that the oom_adj so far takes only 6 values (although I am confident that it can take more than that). Haven't experimented enough to validate that, but I shouldn't need to as assigning different oom_adj should be a given for all the app categories. This is to make the LMK intelligent enough to determine which app to kill first rather than grouping different app categories into one priority, in which a lot of popular LMK settings that devs provide do that.
And for the Dalvik LMK, my understanding is that it will remove all dalvik caches of <INSERT_APP_CATEGORY_ADJ> or higher if free RAM/pages reaches the level specified.
Hence, two things are learned here:
- Linux LMK will kill an app category of that particular RAM level or higher if free RAM drops below a certain level e.g.
Hidden_APP has a minfree of 16384 pages. If pages fall below this level, Empty_App will be killed first, free pages is recalculated, then if RAM is still below that, Hidden_Apps will be killed next.
- Dalvik LMK will clear all dalvik caches in RAM of all the App category if free RAM reaches the level e.g.
SECONDARY_SERVER_MEM is 8192 pages. When RAM reaches 8192 pages, all SECONDARY_SERVER caches are cleared.
Best Practices
Now, how do we tweak both so that it is efficient in doing its job, i.e. LMK.
From my experiments I can safely say that:
- Below 60MB free RAM you will feel lag 5-10% of the time.
- Below 52MB free RAM you will feel lag 5-15% of the time.
- Below 46MB free RAM you will feel lag 15-20% of the time.
- Below 42MB free RAM you will feel lag 20-50% of the time.
- Below 36MB free RAM you will feel lag 100% of the time.
The experience of lag increases exponentially from 60 down to 36MB. Hence, the LMK should be tweaked against that.
Also, it is considered best practices to group oom_adj settings of Linux LMK with the Dalvik LMK as when free RAM drops to that level, both the Linux LMK and Dalvik LMK will work together to free up at both sides.
The 6 oom_adj that can be tuned for Linux minfree also need to be tuned correctly, failing this would make the LMK too aggressive/under aggressive in mid levels (even if your EMPTY_APP is aggressive, if your oom_adj is selected incorrectly, you'll get to a point where memory leak occurs).
Talon LMK - This is obsolete, TalonDev is using ThunderBolt! LMK from 0.5.x
Take for example, the Talon default LMK setting where:
LMK_ADJ is 0,1,2,3,7,15.
It's EMPTY_APP is 15
It's HIDDEN_APP is 5
It's HEAVYWEIGHT, SECONDARY and BACKUP is 3
Last three values of MINFREE is 4096, 9216, 12288.
Where's the issue here? If you noticed it congrats.
If you didn't, here's the issue:
The minfree 12288 is tied to EMPTY_APP which has a OOM_ADJ of 15.
The minfree 9216 is tied to nothing but has a OOM_ADJ of 7
The minfree 4096 is tied to HEAVYWEIGHT,SECONDARY and BACKUP with the OOM_ADJ of 3.
The LMK_ADJ is important as it represents the checkpoints where the Linux kernel will check for minfrees and kill them. Here's a situation:
Memory is below 12288 pages, OOM is triggered and Linux looks for EMPTY_APP to kill and kills all of them. Job done. Memory is back to >12288 pages.
After a few days, memory is below 12288 pages again, OOM kills all EMPTY_APP, but free memory is still lower than that. It sees if the next checkpoint is fulfilled, which is 9216 pages, and yes memory is still below 9216 pages. It looks for an OOM_ADJ of 7 and above to kill, but fails to find any as 7 and above OOM_ADJ only consists of EMPTY_APP.
Here comes the quandary. The next checkpoint is 4096. We're not ever going to reach that as you'll need memory to fall below 16MB, and at that time it'll be super sluggish to even support GUI. Hence BAM, memory leak or lag or something.
Supercharger LMK 512HP - Multitasking
Let me just paste this to avoid a lot of retyping
Code:
FOREGROUND_APP_ADJ=0
VISIBLE_APP_ADJ=4
PERCEPTIBLE_APP_ADJ=2
HEAVY_WEIGHT_APP_ADJ=5
SECONDARY_SERVER_ADJ=6
BACKUP_APP_ADJ=7
HOME_APP_ADJ=1
HIDDEN_APP_MIN_ADJ=8
EMPTY_APP_ADJ=15
FOREGROUND_APP_MEM=1536
VISIBLE_APP_MEM=3072
PERCEPTIBLE_APP_MEM=1024
HEAVY_WEIGHT_APP_MEM=10240
SECONDARY_SERVER_MEM=10240
BACKUP_APP_MEM=15360
HOME_APP_MEM=1024
HIDDEN_APP_MEM=15360
EMPTY_APP_MEM=25600
LMK_ADJ="0,4,6,8,14,15"
LMK_MINFREE="1536,3072,10240,15360,20480,25600"
A few things here:
It's EMPTY_APP and HIDDEN_APP is too large, 80 and 100MB respectively, but the 80MB is a false flag hence it doesn't really matter if you tweak that and you can get a very minor degree of multitasking because of this false flag. I'll get to that in a moment.
It's PERCEPTIBLE_APP has higher OOM_ADJ than VISIBLE_APP (odd selection, but RAM rarely goes below 40MB before it starts lagging like hell) People would reboot their phones when it gets to that, but it rarely gets to that for this configuration as LMK is pretty aggressive here.
Now, it's LMK_ADJ is "0,4,6,8,14,15"
15 is EMPTY_APP,
14 is nothing
8 is HIDDEN_APP - it looks like it'll only kill HIDDEN_APPs when it reaches 60MB, with HIDDEN_APPs being the heavy hitter of apps as most apps will end up in this category. Hence why multitasking is still doable (to an extent) but an aggressive LMK means taking a call or switching to a browser will kill your game (losing saves). Inconvenient, but it works for some people who haven't played a long game without saving and never took a call in between. Imagine the horror LOL!
Juwe's RAM Script
Code:
if [ -e /sys/module/lowmemorykiller/parameters/adj ]; then
echo "0,1,2,4,6,15" > /sys/module/lowmemorykiller/parameters/adj
fi
if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then
echo "2560,4096,5632,10240,11776,14848" > /sys/module/lowmemorykiller/parameters/minfree
fi
No OOM_ADJ are given, hence the stock ones are in effect here.
From init.rc, this is the stock 2.3.5 OOM_ADJ.
FOREGROUND 0
VISIBLE, PERCEPTIBLE 1
HEAVY_WEIGHT, SECONDARY_SERVER, BACKUP 2
HOME 4
HIDDEN_APP 7
EMPTY_APP 15
This one also suffers from the false flag of the 2nd last minfree not being used. It will start killing HIDDEN_APP at 40MB, which is usable (you'll only get lags 15-20% of the time, and most probably after long usage). Other than that, it's pretty stable.
Misc
There are a few known scripts that tweaks the LMK as well as the app priority (yes, the priority of the process categories can be changed too by using setprop.)
Supercharger is one of them:
http://forum.xda-developers.com/showthread.php?t=991276
Take note that Talon doesn't permit Supercharger to be used (it will override it when booting through boot scripts) as Talon itself uses its own LMK settings that are optimized for ZRAM/Swap.
Kickasskernel script is also included in Supercharger. The script will clash with Zach's script in ThunderBolt! too as both of them tries to set different values for the same settings.
Note that Zach's script doesn't tweak LMK settings as i9000 Talon doesn't permit it. With that, if you're using Zach's scripts, you would need to find other ways of tweaking the LMK. Using Auto Memory Manager is good. You can download Supercharger, look at the presets and apply it using Auto Memory Manager. The preset is the only thing important here
LMK App Category Priorities
Using setprop, there is a way to set the priorities of the category. Since, app categories are different, I can only offer one recommendation: The HOME_APP_ADJ.
This prop setting sets how high of a priority your launcher is. A 1 or 2 is sufficient to make sure your launcher doesn't get killed. However, do you really want it to be on 1 or 2. Based on the previous article (LMK/OOM), you would know that OOM priorities are comparatively based on one another. Setting it 1 or 2 in stock 2.3.5 values would basically override PERCEPTIBLE/VISIBLE app priorities. Do you want your launcher to be killed only after your keyboard/music player to be killed? You decide
Journaling/Barriers
This has been a touchy subject here in XDA for most people who debate about it. Most recently, the SAS/Acid tweaks included a way to disable journaling on these partitions:
/system (System is read only, it's safe to remove journaling. However, you will not see speed increase by removing it as you're not writing onto /system 99.99% of the time unless you're using Titanium backup to remove system apps or copying init.d scripts to it)
/cache (Cache can be rebuilt on the fly. Data corruption on it is not game breaking)
/data (All of your data on your phone is here. Removing journaling can risk data corruption. Read more below)
On whether we need journaling or not, I will pose this situation:
Journaling is required to maintain data consistency in events that could lead to data corruption. Data could get corrupted in a number of situations:
- Misbehaving app that constantly writes without syncing/committing data to the disk
- Power loss due to forced reboots or bootloops when data is partially written/committed into disk
Android will normally buffer its writes before committing to the disk. This way, data stays in the RAM before data would only get written into the disk after a period of time. Take note that we as Android enthusiasts seek ways to better our phone to get the most out of it through experimental and sometimes wacky ways. Take OC/UV for example. When we OCed or UVed too much, sometimes our phone will get deadsleep or constant reboots. This leads to corruption if journaling is not turned on. However, we can get corruption too even with journaling but the risk is smaller.
Mount options too, play a role in whether journaling can be safe/unsafe. Most lagfixes will place a "barrier=1" in the /data to make sure that journals are actually committed before an out-of-order write is done. With that, the risk is greatly reduced at the cost of performance. You could experiment by removing barriers and see if it works for you. No guarantees on data if you remove barriers! More info on ext4/barriers:
http://lwn.net/Articles/283161/
http://kernelnewbies.org/Ext4#head-25c0a1275a571f7332fa196d4437c38e79f39f63
If you do disable journaling, make sure to manually run an fsck on your disk. Make sure the fsck binaries are in your binary paths (echo $PATH to show your binary paths). Don't ask how to do this if you're unable to do fsck. It is your own risk that you are disabling journaling/barriers.
One experiencing I would like to relate is this:
I've personally disabled ext4 journaling on my device. After experiencing a sudden power loss (forced reboot), my apps started FCing left and right and device became unstable that it sometimes rebooted when the device is sleeping. In other words, it's a lost case. Reflashing was the only way to restore my phone. This happened 1 day after disabling my journals.
Also note that ext2 is basically an ext4 without journaling. However, ext4 is updated all the time while ext2 source is not updated for quite some time (2 or 3 years?). Most optimizations are already in ext4 while ext2 even without journaling is slower than ext4 without journaling. A comparison of performance:
No journal:
ext4 > ext2
With Journal:
ext2 (can't do journaling in ext2) > ext4 > ext3
Update: Attached is a JournalingOn.zip for i9000 only that you can flash to rejournal your partitions (Only for i9000 devices!). Also attached is Acid Tweaksv6 - Removed Useless Stuff that will disable journaling only for /system and /cache, if anyone is interested. You will need to rejournal first before unjournaling. To be sure that /system and /cache has no journaling and your mounts are applied correctly, type "mount" without the quotes.
You'll be able to see that /data will have:
Code:
barrier=1, data=ordered
/system and /cache will have:
Code:
barrier=0, data=writeback
To be really sure, you can check by using tune2fs included in both the JournalingOn.zip and Acid Tweaksv6 - Removed Useless Stuff.zip.
Copy the tune2fs to /tmp and set rwxr-xr-x as its permissions using Root Explorer/File Expert
Code:
/tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You can substitute the /dev/block/mmcblk0p2 (which is /data) to /dev/block/stl10 (/dbdata) /dev/block/stl9 (/system) /dev/block/stl11 (/cache) to check each partition.
Continued in Post #2 - Lack of space
Still posting ...

Undervolting/Overclocking
This is also another touchy subject, but more towards people complaining about phones that get forced reboots or bootloops. OCing is done to get better performance on your android. WARNING: Ocing will cause more wear and tear on your CPU and will reduce your CPU lifetime. How much it will reduce it? No one knows. It depends on how sturdy your CPU is, and that cannot be measured by any means. It could be reducing months out of year e.g. 6months out of 3 years? No one actually knows.
UVing on the other hand reduces battery drain especially when you UV your 100MHz as 90% of the time in normal usage, your CPU will idle at 100MHz. How much can it save? No one actually did a benchmark on it. Save to say, UVing does not harm your CPU, it will actually extend the life of it by reducing wear and tear Oh, bootloops do corrupt data if you're without journaling
Always remember to clear your UV/OC settings before flashing another kernel!
Take note that the ability to OC/UV depend on your phone. Some SGS can UV better or OC better and some might not.
On how to UV:
1. You can UV more on the lower frequencies than the higher frequencies.
2. Do a UV for
100MHz with (950-150=800) - Take note that 950 is the base value for the voltage. Some kernels might have changed this value to 925 or 900. This is why clearing your OC/UV settings is important as the OC/UV settings will only load the voltage difference, which in this case -150. If the base voltage is 900 and you do a -150 for it, you'll end up with 750 which might cause bootloops.
3. Limit the max frequency to 100MHz. WARNING: Doing this will significantly slow down your system to a crawl, but it is still running. This is done only to test the stability of your system. You can skip this if you want, but you would need to find a way to stress test your CPU at the 100MHz value (and other values as well by limiting the max frequency). Failing in testing this will result in deadsleeping (as your phone is in 100MHz when you sleep and if you undervolt too much, you deadsleep)
3. Test with RockPlayer (or MX Video Player) and play an RMVB file using software decoding for 10mins. If your settings is unstable, Android will freeze up and reboot. (this is just an example, but I find that this way stresses the CPU to the max. I fail to find another way of stressing it as even playing NFS is stable on some voltages but fails when I play rockplayer. Hence rockplayer is the best way so far)
4. After doing this, remove the limit and move on with the next few frequencies.
The rest of the voltages, just rinse and repeat.
200MHz with (950-100 = 850)
400MHz with (1050-75 = 975)
800MHz with (1200-25= 1175)
1000MHz with (no change)
You can experiment with lesser values than these if you get freezes/bootloops as this is by no means a one size fits all value. Some might think this UV is overly aggressive or some might think that this UV value is too underwhelming.
Mine if you're interested:
Code:
100MHz = -200 (950 base)
200MHz = -150 (950 base)
400MHz = -125 (1050 base)
800MHz = -75 (1200 base)
1000MHz = -50 (1275 base)
As for OCing, you would do the same to test the stability. Just that you will be enabling a higher clock for your L0 frequency (L0 is the highest frequency). Some kernels might add more frequency states i.e. from the 5 states above to 6. You can try using Tegrak OC app too. It all depends on your own experimentation.
Memory Leaks
If you found out that your Android is laggy after sometime and a reboot will make it faster, then you're experiencing memory leaks. "free" is a command to show your currently free memory. It will not necessarily be the same value as your phone's free memory (as it takes into account swaps and buffers)
1. Go to terminal emulator (or download the script at Post #3)
Code:
su <ENTER>
free <ENTER>
This will show your buffers and free memory.
My example:
Code:
total used free shared buffers
Mem: 348548 340280 8268 0 1320
Swap: 163836 47292 116544
Total: 512384 387572 124812
Then do this:
Code:
sync <ENTER>
echo 3 > /proc/sys/vm/drop_caches <ENTER>
Type:
Code:
free<ENTER>
And you'll realize that the buffers will reduce and free memory will increase, like this example:
Code:
total used free shared buffers
Mem: 348548 305212 43336 0 88
Swap: 163836 46804 117032
Total: 512384 352016 160368
That means it's done.
Click to expand...
Click to collapse
If this solves the laggginess problem, it's due to vfs_cache_pressure being too low and dirty_ratio being too high. However, in most cases, you don't have to do this as Linux will manage to clear the RAM in a timely manner as long as there are no apps that constantly hold on to the memory (not releasing it). Hence, only do this when necessary (lagginess and such).
With that, I've updated the system_tweak yet again, with this knowledge by making the VM settings more aggressive, which will trigger the memory leak faster. I made this so, as there's a workaround to clear the caches when it gets full.
Having a low vfs_cache_pressure and a high dirty_ratio will save battery and make your device perform faster at the cost of higher RAM usage.
You can actually automate it by using Script Manager by making a script, pasting the instructions and making a widget out of it. To learn more, read the android market description or the in-help guide in the app.
Some commonly asked questions about drop_caches that were answered by me from flolep:
http://forum.xda-developers.com/showpost.php?p=17727859&postcount=3428
http://forum.xda-developers.com/showpost.php?p=17731938&postcount=3446
http://forum.xda-developers.com/showpost.php?p=17736421&postcount=3450
Checking for Battery Drain/ Saving battery
Starting from Gingerbread, you can't really look for Partial wakelocks anymore to determine what is draining your battery at night. BetterBatteryStats is a way to check for that. It also can provide the process that drains your battery most of the time.
A high partial wakelock usually says that something is waking up your phone at night. With that, checking partial wakelock, you can see if these are the culprit:
-Network Location
-Location Manager Service
If so, disable Lattitude or any location check-in app that you're using. It's checking you in every few minutes that drains the battery.
Disabling Wifi/3G/HSDPA saves battery too. I find that Wifi/Edge drains the least amount of battery when idling. To switch to EDGE as opposed to HSDPA/3G.
Go to:
Code:
Settings > Wireless > Mobile Networks > Network Mode > GSM Only
Disabling "Use Wireless Networks" in location and security would save a little bit of battery too I guess. It's in:
Code:
Settings > Locations and Security > Use wireless networks
CSC
CSC is a folder that defines your APN settings and country/region specific configurations aside from Language/Time that is configured in build.prop(also for Samsung Apps).
Having to manually set your APN is annoying right?
Your product code being KOR by default is another annoying thing to deal with. How do I resolve this?
1. Get your CSC from your own country here: http://forum.xda-developers.com/showthread.php?t=948790
2. Extract from the zip file /system/csc/<folder> (where <folder> is your Country's CSC)
3. Use Root Explorer/File Expert to copy it to the phone's /system/csc/.
4. Use nitrality to change your product code. WARNING: This will wipe all your data.
Odexed vs Deodexed
I've been using Deodexed ROMs since I first flash my custom ROMs. One gripe I have is that I seem to have lost the stock smoothness/speed that I experience when I'm using a stock ROM. I found out that deodexing actually extracts the customization files back to the APK (using APK manager) and Odexed files are actually done to optimize the speed of those files itself.
The only reason ROM chefs are using deodexed files is that it is easier to theme. There is no need to decompile the odex files and make the changes as all the theme files are in the APK themselves.
Only other reason that I know of is the overscroll glow. Odexed files can't support it. However, that is a small price to pay for speed/smoothness that I am willing to sacrifice.
Busybox
Busybox is required to perform all of your superuser activities in your android phone. There are some problems associated with this when ROM developers decide to use a certain version of Busybox that are incompatible with the binaries that we use in our phones. When you found out that after changing your kernel/ROM:
- You still have superuser and Titanium Backup still works but,
- Root Explorer/File Expert can't copy files correctly to the /system after mounting rw
- Voltage Control/ Pimp My CPU/ Control Freak/ SetCPU cannot create the Svolt_scheduler file in /etc/init.d
You have a clashing busybox version issue. This can be remedied by:
- Installing the busybox installer from the market
- Installing busybox 1.17.x into /xbin
- Removing all other busybox binaries from your binary path. (This is optional if you found out that after installing busybox, everything works. Try it first before removing) To know your binary path, do an
Code:
echo $PATH
Nandroid Backup
Nandroid Backup is done in recovery (VolumeUp + Home + Power). In recovery, choose Backup And Restore. What it does is it backs up your:
- Boot
- System
- Data
- Cache
When you restore, you should preferably use Advanced restore and restore the /system and /data. All others can be built from scratch (except /boot). If you're converting from CM7 to Samsung Roms, it's best to start from scratch either ways. Restoring nandroid from any is considered dangerous and not supported by most cases. Best is to use Titanium Backup to backup as it can be restored both ways (only restore app though, restore data sometimes can lead to FCs)
Voodoo Color
Voodoo Color is also a point of contention among users. Some like it and some hate it with a passion. If your kernel does support it, here's a way to tweak it:
1. Tweak the color profiles. Can't see a difference, hence I would just pick Voodoo most of the time.
2. Tweak the gamma first to a comfortable value. I.e. drag the 3 sliders together to a comfortable gamma level. After that, try looking in the gradient (the gray slab below the slider) and try to find for neutral gray values. Adjust each slider until you find a neutral gray (i.e. left and right until you see that slab is truly gray)
3. Tweak the RGB multiplier until you have a comfortable level (3 sliders together). Then tweak it the same by referring to the gradient until you're comfortable.
4. Switch off your display for a while and look at your surroundings to reset your eyes. Then turn on your screen again and see if its too green/yellow/blue etc. Adjust the gamma/RGB multiplier until you're satisfied.
This might take a few rounds of testing, but in the end you'll be truly satisfied with it
i9000 Specific
i9000 Kernels - In Depth
You will need to have a stock odexed (why odexed? read a few passages below)ROM with root. You can easily do this by flashing stock XXJVS 2.3.5 and then flashing a custom kernel through Odin like:
- Dark Core - Uses Voodoo initramfs
- CF-root - Uses CF-root initramfs
- Semaphore - Uses CF-root initramfs
- Midnight - Uses Speedmod initramfs
- Galaxian - Uses CF-root initramfs
- Voodoo - Uses Voodoo initramfs
You can flash the custom kernel through Odin by placing the tar file into the PDA section and pressing Start. At this point, do not convert your partitions to ext4 (lagfix) unless you're using a Voodoo based initramfs as Voodoo based initramfs will convert your partitions to ext4 automatically at first boot.
After flashing a custom kernel through Odin, you will gain root. From there, you can choose to use any other custom kernels that use CWM to install or stick with the custom kernel that you've flashed through Odin like:
- TalonDev - Uses Voodoo initramfs
- TalonSH - Uses Voodoo initramfs
There are other kernels as well, but since I did not stress test them, I will not include them here. This thread lists the full repertoire of custom kernels that you can choose from:
http://forum.xda-developers.com/showthread.php?t=1196704
On which custom kernel to pick, you're advised to look at the individual threads original post as well as the last 5 pages of the thread to know about its stability and features. I pick TalonDev myself as it has compache as well as the latest upstream (kernel updates from the Linux OS as well as the official Android Open Source Project/AOSP and optimizations) patches.
At this point, you should decide if you would want to convert to ext4 (lagfix) or not. Your phone by default will reside in an RFS system. The RFS at this point in time is pretty stable and its performance can easily match ext4. Too bad Quadrant scores are bad for RFS, but who cares about Quadrant anyways. I myself choose to use ext4 as the TalonDev kernel has a lot of ext4 upstream patches that optimizes the usage of ext4 on Android.
If you're using Voodoo initramfs, you'll be converted to ext4 automatically.
If you're using CF-root initramfs, you will require the CF-root ext4 app to convert that can be found here:
http://forum.xda-developers.com/showpost.php?p=12651371&postcount=7
Note that on some kernels that use CF-root initramfs, the ext4 app will warn you that you're not on CF-root type kernels. Ignore this warning. You'll be able to convert to ext4 anyways unless you're on Galaxian. Certain Galaxian versions (since the kernels are not versioned, I can't tell which versions are not working) will bar you from converting to ext4 using the ext4 app. If that is the case, just flash CF-root, convert to ext4 and then flash back to Galaxian.
Also not that CF-root based initramfs kernels will remove your bootsounds on first boot. Don't be alarmed by this.
In terms of which lagfix is better (Voodoo vs CF-root lagfix), I can't tell at this point in time. Both are equally good. Since TalonDev uses the Voodoo initramfs, I am inclined to use the same when I am using the same kernel. That should be a good yardstick to follow.
BIGMEM/ Non-BIGMEM:
Some kernel developers released BIGMEM versions of their kernel:
-TalonDev BIGMEM
-TalonSH BIGMEM
-Semaphore bm version
The only difference a bigmem kernel can bring is more memory at the expense of 720p video recording. Playing a 720p video is still possible. Recording it is not on a bigmem kernel. Bigmem kernels normally have 13MB more than their non-bigmem counterparts. How this 13MB could affect you? It depends on the apps you use and how aggressive your LowMemoryKiller is.
XXJVT System apps
System apps can be frozen/removed to make your system faster/less battery draining.
In order to remove/freeze system apps, you would need Titanium Backup (Pro) or System Tuner.
The choice whether we want to remove or freeze the system apps should now be decided. Titanium Backup Pro and System Tuner uses a built in Android mechanism to freeze your system apps - PM disable. PM disable will actually disable the app from the system itself. It will not drain the battery or even launch itself. It is a safer way so to speak. Removing will physically delete the APK app from the system freeing up disk space. If you decide to remove, make sure to have a backup before proceeding. Even if you have a backup, restoring from Titanium Backup may sometime fail. Hence, do this only if you're sure you want to remove that certain app. Freezing an app will make it easier to defrost without any consequences.
Here are the apps that I disabled:
Code:
AngryGPS > Used to manually configure GPS. Not needed if GPS works OK.
BluetoothTest
Buddies Now
lcdtest
screencapture > Screen capture app
Daily Briefing
Days
EncryptApp
Factory Test
Gallery -> I use QuickPic as a replacement. It's faster than Gallery.
Google Partner Setup
Google Search > Google search widget
Home screen tips
HTML Viewer
Market Feedback Agent
Market Updater > I froze this to avoid being updated to Market 3.0. It currently sucks now
Mobile tracker > Mobile tracker, only if you use it, then keep it
Mobile tracker settings > Mobile tracker, only if you use it, then keep it
Perso
PhoneSetupWizard > Required if you're first booting/installing the ROM, not needed afterwards
PopupuiReceiver
Press Reader
Print via Bluetooth
RoseEuKor
Samsung Account
Samsung Keypad -> I use Swype beta instead
Self Test Mode
Service mode
SimDetachNotifier > Will notify you if you detached your sim card. Seems pointless
SNS > Only necessary to sync your contacts if you're using Social hub to do so or syncing calendar from Facebook
SNSAccount > Same as above
Social Hub
Software Update
Synchronise
TwLauncher -> Using Go Launcher Ex instead
wipeoutreceiver > Wipe if phone is stolen. Not needed if you don't use the Samsung service
WlanTest
wssyncmlnps
There are others that you can remove as well. I'm hoping to gather feedback on the other APKs that can be removed and what will be affected by its removal. Please post if you have more information
Disabling Lagfix
Most ROMs would advice you to disable lagfix before flashing a new ROM. Although this is not necessary in most cases (as all Gingerbread kernels support ext4 from the get-go) moving from one kernel to another might need it (to optimize the initramfs it is used on). Hence if you're swapping from one kernel (that has a different initramfs) to another. It is adviseable to undo the lagfix.
CF's lagfix can be undone by using the ext4 app.
Voodoo lagfix can be undone by using the Voodoo Control App.
Speedmod lagfix can be undone by using it's recovery.
Odexed ROM
You might say, hey if I'm using stock, I'll be missing extended power menu, battery percentage and all other theme mods that are not in the stock ROM. Fear not, you can get all these back including Gtalk2, CRT screen off etc here:
$omator's stock+
Gtalk2
There are odexed themes too, in which the developers would decompile the odex files into APKs, make the changes then compile the APKs into odex files again. It is more tedious than deodexed themes but odexing generally makes the phone smoother
You can find the themes here:
http://forum.xda-developers.com/forumdisplay.php?f=666
WIFI Issue on JVR/JVS/JVT
You might be facing some wifi connectivity issues on JVR/JVS/JVT ROMs i.e. it disconnects every few seconds.
This is due to some changes in the ROM that doesn't permit a "Forever" lease time from your modem. Change your lease time to an hour (or two) or if you don't have that option, remove your address reservation option from your modem (Yes, it's a modem only tweak, nothing you can do on your phone)
Memory Freak
Memory Freak is an app in TalonDev that tweaks the ZRAM/Swap and LMK settings. There's a golden rule to the ZRAM/Swap that is:
Swapping to and from the ZRAM will be slower if the amount of ZRAM is more than 50% of the total usable memory, . Hence, I set mine to 160MB (from the 340 total usable RAM). Swappiness in most Linux machines is 60. This means, the system will be inclined to swap in/out more than just using the RAM. I set mine to 50 as a personal preference so that there would be 50% chance that the system will use swap or RAM.
HiddenApp is the amount of free memory to be when LMK starts looking for hiddenapps to kill. I set mine to 52 for my multitasking preference. Experiment with it to see how much multitasking vs smoothness you're looking for. My preference will change in time. Check my signature for the most updated ones.
WIP:
This is obviously a work in progress article that will undergo changes as the Android scene improves. I will spend time to make edits and additions to the post whenever I see fit. Sometimes I will post changelogs at the end of the thread, sometimes I won't if I only make minor edits. Just be sure to check back often to see any new tips offered
Credits:
I claim no credit on these findings except for the ones that I've researched on my own. However, all of it is not of original work since I form my own opinions after reading a lot. I also don't claim that the settings I posted are the most optimal there is. It might not even work well for most of you guys. The key here is tweaking it to your own perfection as there is no setting that will cater to everyone's needs. Hence the real people who deserve credits are:
* All the devs' kernel/apps that I posted here
* XDA forum
* Google
Attention!
If you're looking for scripts, here it is:
[CWM][SCRIPTS][TWEAKS] Thunderbolt!
Script Reviews are here:
Script Reviews
GUIDE UPDATES
UPDATE 1/10/12
* Edited some sections with some new knowledge that I have. A few places, can't name them all Check them out and see if you can spot them.
UPDATE 10/19/11
* Moved around some guides and grouped them together
* Updated some guides to make them more Android centric (as opposed to i9000 centric)
UPDATE 10/18/2011 - Added an indepth article about LMK/OOM. CTRL-F for LMK.
UPDATE 10/12/2011
* Added some comments on the apps removed/frozen so that you can make an informed choice of why the apps can be removed/frozen.
* Added my analysis of most schedulers that I know of and why they are good/bad.
* Moved the scripts to ThunderBolt!: LINK
* Added a guide on the wifi issue for JVR/JVS/JVT
UPDATE 10/1/2011 - Moved the script reviews to this post LINK
UPDATE 9/23/2011:
* Removed the JournalingOn.zip and Acid Tweaksv6 - Removed Useless Stuff.zip because people might use it for devices other than the i9000. This is because in other devices such as SGS4G, the /dev/block/stl10 is /data while in i9000 it's /dbdata. The JournalingOn.zip will not enable journaling on /dbdata without some editing. Hence, I removed it as I don't have a time to put up a warning or notice, and didn't have time to edit the script inside the zip file.
* Readded an edited JournalingOn.zip and readded the Acid Tweaksv6 - Removed Useless Stuff.zip (did not change) to the first post. Only for i9000 devices!!
* Added another way to check if you're journaled or unjournaled. Check the guide below.
* Added some more explanation on common scripts I found.
* Moved the guides around due to lack of space. I added some minor changes to most of the guides. See if you can detect them

Reserved - 10 char

Reserved - 10 char again ...

Changed the name to get more attention. Surprised that no one gave a comment about it
Appreciate any comments or criticisms or correction of what I've written here.
Thanks!

Excellent Read!
Thank you very much!

carnagecjb said:
Excellent Read!
Thank you very much!
Click to expand...
Click to collapse
Glad you enjoyed it

this is actually really helpful. half the time I really didnt know what I was messing around with thanks.

Dataslycer said:
this is actually really helpful. half the time I really didnt know what I was messing around with thanks.
Click to expand...
Click to collapse
Cool Glad that you liked it.
Hope this gets more attention as I would want it to be beneficial to people who uses tweaks and to know how to use them

Nice read Mate. I used to wonder about I/O schedulers and which one to use etc. I like to add build.prop scripts and int.d scripts. This thread just helped me to understand more about it.
Thanks!

read every word, thank you very much. I'll be talking to my kernel dev about BIGRAM... on miui our 720p recording doesn't work right anyways. Thanks again for the great info.
Sent from my MIUI SCH-i500

ShyamSasi said:
Nice read Mate. I used to wonder about I/O schedulers and which one to use etc. I like to add build.prop scripts and int.d scripts. This thread just helped me to understand more about it.
Thanks!
Click to expand...
Click to collapse
Thank you for reading. Hope the knowledge comes in handy when you tweak your phone
sageDieu said:
read every word, thank you very much. I'll be talking to my kernel dev about BIGRAM... on miui our 720p recording doesn't work right anyways. Thanks again for the great info.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Wow, great! Hope you enjoy reading it as much as I enjoyed writing it

having trouble with your thunderbolt tweak. I downloaded the file for I9000 placed it on my phone (SD card) mounted my system and data in recovery mode then proceeded to install the thunderbolt zip file. Using script manager i found the bolt_scripts file and ticked the run at boot button. Then i hit the run button and got 14 permission denied messages asking are you root. Do i have to run this as root. Might be a dumb question but im very new to trying this. Thanks

kevnac said:
having trouble with your thunderbolt tweak. I downloaded the file for I9000 placed it on my phone (SD card) mounted my system and data in recovery mode then proceeded to install the thunderbolt zip file. Using script manager i found the bolt_scripts file and ticked the run at boot button. Then i hit the run button and got 14 permission denied messages asking are you root. Do i have to run this as root. Might be a dumb question but im very new to trying this. Thanks
Click to expand...
Click to collapse
Yes, you need to run everything as root . Scripts in init.d would already be running as root. You just need to make sure Script Manager is running as root for the remount script

Excellent thread, very well written, had a quick skim read, but I'm going to take some time tonight to absorb it all ;-).
Thank you!

zeekiz said:
Excellent thread, very well written, had a quick skim read, but I'm going to take some time tonight to absorb it all ;-).
Thank you!
Click to expand...
Click to collapse
Cool Thank you for reading such a long article
Let me know if you have any questions or if you think I made a mistake

superb thread !

testomat said:
superb thread !
Click to expand...
Click to collapse
Thank you for reading

testomat said:
superb thread !
Click to expand...
Click to collapse
+1
10 chars

rom-g said:
+1
10 chars
Click to expand...
Click to collapse
Thank you for the support

[DATABASE] Best Root Apps [Updated 03 nov]

Most of you might be very much familiar with the rooting procedure. Its the process of giving yourself superuser permissions (ex - administrator in windows xp ).
If you are using a custom rom, then there is no need to specifically root your phone. But if you are using stock roms, then there is a guide to root in the forums.
Once rooted, you can now take your own decisions for your device which include improving system performance or flashing custom roms using cwm recovery or using any of these below listed apps. Use it wisely, as playing with your device performance can have damaging effects.
I AM NOT AT ALL RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE BY YOU.
Moving on, many of the rooted-on-stock and custom rom users might already know most of these apps and their uses, so this thread is for the beginners who have just rooted their devices.
Further, most of these apps are available in the playstore (mostly paid, but if you want the cracked versions, you can find them in the internet.
So here are some of the apps that might be useful for you. I will also update this apps list as soon as, I find more useful apps.
SPECIAL THANKS TO Android_United
Original Thread:Link
HIT THANKS IF YOU LIKE THIS THREAD.
TITANIUM BACKUP ROOT
{
"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"
}
Description
EXTREMELY powerful tool. Backup ALL apps, Market links, remove bloatware & MORE!
☆Needs ROOT, Android 1.5-4.1+ (ARM,x86,MIPS)
☆Over 6.5 million users, 29+ languages.
☆PRO Key is available on Play Store!
☆Voted #1 TOP ROOT APP on Twitter.
☆Problem? See titaniumtrack.com/kb
☆Scroll down for more info & DEMO VIDEOS
☆ ☆ ☆
Titanium Backup is the most powerful backup tool on Android, and then some.
You can backup, restore, freeze (with Pro) your apps + data + Market links. This includes all protected apps & system apps, plus external data on your SD card. You can do 0-click batch & scheduled backups. Backups will operate without closing any apps (with Pro). You can move any app (or app data) to/from the SD card. You can browse any app's data and even query the Market to see detailed information about the app.
Also see the paid PRO key which adds EVEN MORE awesome features such as:
[✔] 0-click batch restores
[✔] Keep multiple backups per app
[✔] Backup/restore SMS,MMS,calls,bookmarks,Wi-Fi AP as XML
[✔] Multi-user app data
[✔] Apps freezer
[✔] Sync to/from Dropbox (manual/scheduled)
[✔] Sync to/from Box (manual/scheduled)
[✔] Sync to/from Google Drive (manual/scheduled)
[✔] Convert user apps <=> system apps
[✔] Integrate system app updates into ROM
[✔] Encryption
[✔] Market Doctor (relink apps to Market)
[✔] "Destroy all Market links" feature
[✔] Hypershell speed
[✔] Backup apps without closing them!
[✔] Restore individual apps+data from non-root ADB backups!
[✔] Restore individual apps+data from CWM backups!
[✔] Restore individual apps+data from TWRP backups!
[✔] Market "auto updating" manager
[✔] Dalvik cache cleaner
[✔] Integrate Dalvik cache system elements into ROM
[✔] Unlimited schedules
[✔] Load/Save a Filter and use it in Widgets/Schedules
[✔] Change the device's Android ID, restore it from a backup or after a factory reset
[✔] Protect backup against deletion
[✔] Send backup (to e-mail/cloud) and import it in 1 click
[✔] Backup→Verify→Un-install an app in one shot
[✔] Freeze/defrost/launch apps in a single click
[✔] CSV export any app DB (e-mail or Google Docs)
[✔] Convert app data to/from fast WAL format
[✔] WAY MORE!
Check out this in-depth review of TB PRO:
http://youtube.com/watch?v=vuvDTS9RDrM&hd=1
And check out the new TB PRO demo video:
http://youtube.com/watch?v=YU33zabluSY&hd=1
More info on permissions:
• "Internet" is used to access Market,Dropbox,ChangeLog.
• "Accounts" is used to access Market.
Some advice:
• We recommend to avoid "modified" TB versions because they can cause various problems down the road.
ROOT EXPLORER (File Manager)
Description
Root Explorer is the ultimate file manager for root users. Access the whole of android's file system (including the elusive data folder!).
Features include SQLite database viewer, Text Editor, create and extract zip or tar/gzip files, extract rar archives, multi-select, execute scripts, search, remount, permissions, bookmarks, send files (via email, bluetooth etc), image thumbnails, APK binary XML viewer, change file owner/group, create symbolic link, "Open With" facility, MD5, create shortcuts.
For fast, friendly support simply email us: [email protected]
We will always try to help with any problem you may have with the app. If we can't help then you can have a refund, no questions asked.
Although 14,000+ five star ratings will tell you that most people are very satisfied customers. Make sure you read as many comments as possible to get a good idea of what most people think of the app.
We still respect the old 24 hour refund policy. So if you're not happy with the app just email us within 24 hours and you can have a refund. We'll need to know the order number, which you can find on the emails sent to you by Google when you downloaded.
Why compromise? Get the original and the best!
[root] MOBILE ODIN PRO
Description
Mobile ODIN - Full firmware flashing straight from the device itself!
Mobile ODIN is the on-device firmware flasher of choice. Just throw those firmware files on your (internal or external) SD card, start Mobile ODIN and flash away.
! Your device must be rooted to be able to use Mobile ODIN. Check the list below to see if your device is supported !
If you use the EverRoot option, Mobile ODIN will root the firmware while you flash it. Checking out that new leaked firmware? No reason to lose root!
Currently supported devices:
- Samsung Galaxy S GT-I9000/B/M
- Samsung Galaxy S GT-I9003/L
- AT&T/Rogers Captivate SGH-I896/I897
- Samsung Galaxy S2 GT-I9100/T/G/m
- Samsung Galaxy S2 SHW-M250S/K
- Samsung Galaxy S2 SC-02C
- AT&T Galaxy S2 SGH-I777
- Sprint Epic 4G Touch SPH-D710
- US Cellular Galaxy S2 SCH-R760
- Samsung Galaxy S3 GT-I9300/T
- Samsung Galaxy S3 GT-I9308
- AT&T/Canadia Galaxy S3 SGH-I747/M
- TMOUS Galaxy S3 SGH-T999
- Sprint Galaxy S3 SPH-L710
- VZW Galaxy S3 SCH-I535 (unlock bootloader !)
- US Cellular Galaxy S3 SCH-R530
- Samsung Galaxy S3 LTE SHV-E210S
- Samsung Galaxy S3 LTE GT-I9305
- Google Galaxy Nexus (GSM) Maguro/Yakju/GT-I9250
- Google Galaxy Nexus (CDMA/LTE) Toro/Mysid/SCH-I515 (no cdma radio flashing)
- Samsung Galaxy Note GT-N7000
- Samsung Galaxy Note GT-I9220
- Samsung Galaxy Note GT-N7000B
- Samsung Galaxy Note 2 GT-N7100
- Samsung Galaxy Note 2 LTE GT-N7105
- Samsung Galaxy Note 10.1" GT-N8000
- Samsung Galaxy Note 10.1" Wi-Fi GT-N8010/N8013
- Samsung Galaxy Tab 7" GT-P1000
- Samsung Galaxy Tab 7.0 Plus GT-P6200
- Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210
- Samsung Galaxy Tab 7.0 Plus GT-P6200L
- Samsung Galaxy Tab 7.7" GT-P6800
- Samsung Galaxy Tab 7.7" Wi-Fi GT-P6810
- Samsung Galaxy Tab 10.1" GT-P7500
- Samsung Galaxy Tab 10.1" Wi-Fi GT-P7510
- Samsung Galaxy Tab 2 7" GT-P3100
- Samsung Galaxy Tab 2 7" Wi-Fi GT-P3110/P3113
- Samsung Galaxy Tab 2 10" GT-P5100
- Samsung Galaxy Tab 2 10" Wi-Fi GT-P5110/P5113
- Samsung Galaxy 5 GT-I5500/B/L/T/M
- Samsung Galaxy 5 GT-I5503/T
- Samsung Galaxy 5 GT-I5508
Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear.
For discussion and support: http://forum.xda-developers.com/showthread.php?t=1347899
- MANUAL -
Flashing with Mobile ODIN is easy. You start by starting the app and the app will check your system has everything it needs to continue (like root). It may need to download an additional package, so it is advised you have Wi-Fi available.
Now you should see the main Mobile ODIN screen. It will list a set of partitions. Clicking a partition will allow you to select a file from your SD card to flash to that partition. Do not worry about selecting the wrong file - Mobile ODIN will not let you. Separate files (named after the partition) as well as .tar and .tar.md5 files are supported.
From the desktop ODIN you may be used to "PDA", "PHONE", and "CSC" buttons. All three of these buttons have been replaced by the "Open file ..." button. This button will open the file you select from the SD card, and find all the partitions it can flash inside that file. So if you select a .tar file containing kernel and modem, the Kernel and Modem partitions will be set up to use that .tar file for flashing.
Now that we have selected what we want to flash, if you have the Pro version you can proceed to the EverRoot section. The EverRoot options allows you to root your firmware while it is being flashed. Never again will you be without root! Select here which apps you want to inject in the firmware that is being flashed.
Now that we are all done selecting partitions and configuring EverRoot, we continue to "Flash firmware". Mobile ODIN will gather all the information it needs and perform the flash. Before starting, however, it will check that your battery level is over 50%, and if applicable offer to verify MD5 checksums on the files you have selected to flash. If all is well, it will reboot into recovery mode, and flash the firmware you have selected.
ROM MANAGER
Description
Must have app for any root user. Make backups, flash ROMs, and own your device.
ROM Manager is THE MUST HAVE APP for any Android root user. (Over 3 million downloads and counting!)
* Flash your recovery to the latest and greatest ClockworkMod recovery.
* Manage your ROMs via a handy UI.
* Organize and perform backups and restores from within Android!
* Install ROMs from your SD card.
* Install your favorite ROMs over the air!
Premium Version:
* Premium ROMs
* Receive notifications for when your ROM is updated!
* Automatic backups
* Install from QR Code
* Web Connect
* Support
Do you prefer using only recovery manually? Check out the Touch Recovery in app purchase, for the most advanced recovery available!
Why does ROM Manager ask for account permissions?
Web Connect only needs to access your Google account to connect it to your google account. It can't access any private data or passwords.
Troubleshooting:
Droid users: Stuck at the "M" logo? Flash an alternate recovery and flash back to ClockworkMod.
HTC Users: Flash recovery not working? Try fastbooting a recovery on.
Droid X/2/Pro Users: You must run the Bootstrap application first to use ROM Manager.
Samsung users: You must flash a Clockwork compatible kernel first (see XDA forums)
IF YOU ARE HAVING LICENSE ISSUES, MAKE SURE YOU HAVE THE LATEST VERSION OF FREE (4.0+) AND THE LATEST LICENSE (1.0.7+) INSTALLED!
SETCPU for Root Users
Description
Supercharge your Android device with SetCPU. A must-have tool for root users.
SetCPU is a tool for changing the CPU settings on a rooted Android phone or tablet, including the Galaxy Nexus, HTC One series, Nexus S, Nexus One, Motorola Droid, Samsung Galaxy series, and most other devices. You're under control: SetCPU can improve your performance, save battery, or both!
Automate SetCPU with profiles! SetCPU allows you to set up powerful profiles to change your settings under certain conditions, such as what app is running, when the phone is asleep or charging, when the battery level drops below a certain point, when the phone's temperature is too high, or during certain times of day. See the screenshots for examples of how you might set up profiles.
SetCPU's wide feature set make it useful to Android beginners and enthusiasts alike. Accelerate your processor to unleash your phone's true multitasking potential, or dial your CPU's speed down to save battery.
SetCPU also includes a "voltage control" menu, available to certain devices with custom kernels that support it, to control undervolting to save even more battery. Keep in mind that undervolting is only available for certain kernels.
Recent Changes:
Additional permission: Read logs is used for efficient app condition checking. That is currently all it's used for.
3.0.0:
Profiles tab
- Completely rewrote profiles.
- Older profiles will automatically be converted into new profiles.
- Added app and day of week in addition to the older conditions, and more are coming.
- Profiles now support combining conditions under logical trees, with nestable "and," "or," and "not" operators available. It is now possible to easily build complex profiles that take the place of multiple profiles in the older version.
- Actions can now be selected individually.
- Profiles can now be marked as "non-exclusive," which means they will not block profiles with lower priorities from evaluating. In this case, the profiles with lower priorities will perform only actions which have not been performed by profiles with higher priorities. SetCPU will keep evaluating profiles until it reaches an "exclusive" profile that evaluates as true.
- All number selectors in profiles are now in the style of the frequency selector in the main tab.
- The new file extension for exported profile settings is ".setcpu.json."
- To prevent ambiguous situations, it's no longer possible to select priorities that have been used by other profiles.
- The CPU temperature sensor on OMAP4 and some other devices should now be supported for profiles. The option will appear if available.
- Notifications are now set as an action per profile and can now be non-persistent.
- SetCPU will still use the main screen as a "default profile" to set if no other profiles are active. It is now possible to specify an alternate default profile by creating an exclusive profile with no conditions at priority 0.
- SetCPU now asks for a file name before backing up profiles to storage.
- It is now possible to share profiles without having the internal/external storage mounted.
Main tab
- IO scheduler selection has been added via a drop down menu in the main tab.
Bugfixes
- Fixed a bug where the short benchmark always reported 0 ms.
- Fixed the labels in the pie graph in system info.
- Fixed some common crashes.
Permissions:
Root: SetCPU needs root permissions to modify the CPU speed and other settings.
Start at boot: SetCPU will start a profiles service at boot, if enabled. It also sets default boot settings, if enabled. SetCPU does not run in the background if profiles are not enabled, and becomes inactive after settings, if any, are applied.
Wake lock: This prevents the phone from sleeping while stress testing and benchmarking.
Write external storage: SetCPU needs to read from and write to the SD card or internal storage to back up profiles.
Read phone state: The "in call" condition needs this to determine if the user is making a phone call or not, and trigger the profile if the user wants to.
BUTTON SAVIOR (Root)
Description
Requires root for full function. Some keys can still work without root.
Top 1 Software key App on Android Market
Top 10 Must have app for root devices
Top 1 Must have app on HTC HD2
Top 1 Software key app with best customization features
Works from 1.5 to 4.0(ICS)
If you are afraid of breaking your hardware keys or you have broken keys or you simply just don't have any key on your device, get Button Savior to make your life easier.
This app will display a floating software key panel which can be summoned everywhere anytime. Button Savior 1.1.6 or later now suppports E-INK display with specially made themes provided by XDA member Berlinski.
For non root user: You can still use power off, Home, Camera, Call , and volume keys.
[Features]
☆ Simulates 'Home' 'Back' 'Search' 'Back' 'Recent Task' 'Screen Off' 'Volume'
☆ Can set to always open or auto hide based on user customizable timer
☆ Two types of trigger action to choose from (Gesture trigger and Click trigger)
☆ Added Camera key and Call key simulation
☆ Customizable trigger position
☆ Also provides themese to support e-ink display
☆ Can change it to one click mode for super fast button action in option
☆ Can create shortcut action such as call someone or go to bookmark on Call or Camera keys. (With PRO)
[Not Root?]
☆ Home key is supported
☆ Power key is supported
☆ Volume key is supported
☆ Camera key is supported
☆ Call key is supported
IF YOU HAVE PROBLEM GRANTING ROOT FOR THIS APP
If your device is rooted and still cannot use keys except home, please update su binary and superuser apk.
IF YOU ARE UNABLE TO UNINSTALL
You need to disable screen off feature first. To disable, go to setting/location secuirty/device admin to remove Button Savior from the list.
Theme contribution list:
(1) Default (XDA member stefen)
(2) Froyo (XDA member hlvl)
(3) Sense UI (XDA member internauta2000)
(4) Honeycomb (XDA member securecrt)
(5) Pen's Ginger (XDA member Pens and DreamS)
(6) Pen's Honeycomb (XDA member Pens and DreamS)
(7) Pen's Sense UI (XDA member Pens and DreamS)
(8) Contrast for E-INK (XDA member OMGWTF_BBQ aka BerlinSki)
(9) Metro for E-INK (XDA member OMGWTF_BBQ aka BerlinSki)
(10) Subtle for E-INK (XDA member OMGWTF_BBQ aka BerlinSki)
(11) K3 ICS (XDA member kam333)
(12) K3 Honeycomb (XDA member kam333)
[This app requires following permission because]
☆ GET TASK: Need to display recent app
☆ VIBRATE: For hepatic feedback
☆ INTERNET: For ads and for shortcut with internet action
☆ ACCESS NETWORK: For ads
☆ MAKE CALL: For direct dial shortcut
[root] CHAINFIRE3D
Description
Chainfire3D - Take control of your GPU (OpenGL) !
Take control over your GPU!
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!
!! Chainfire3D is for 1ghz+ devices only !!
!! ROOT is required for this program, as well as a writable /system partition. S-OFF is also required on HTC devices !!
Features include reducing texture size and quality to reduce memory use and potentially increase game performance, as well as increasing memory use potentially increase performance.
If you also install the (experimental) EGL driver, AND your GPU supports it, AND you have the Pro version, you can enable 4xMSAA or 16xMSAA on a per-app bases. This can drastically improve image quality!
Be sure to check the thread on XDA for available plugins !
( http://forum.xda-developers.com/showthread.php?t=1087427 )
Chainfire3D has been tested on:
- HTC HD2
- Samsung Galaxy S
- Samsung Galaxy Tab 7"
- Samsung Galaxy S II
- Samsung Galaxy Note
- Samsung Epic 4G
- Motorola Atrix 4G
- Motorola Droid 2
- LG Optimus 2X
- Google Nexus S
Many users are running Chainfire3D on devices not listed here - it's likely to work on all modern devices. So far nobody has reported a failed install, so that's good. Doesn't mean problems can't happen.
!! There is some risk involved installing the driver. Your device may not boot. If you have CWM, it would be prudent to create a backup before installing !!
SUPER SU
Description
SuperSU is the Superuser access management tool of the future
!!! SuperSU requires a rooted device !!!
SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. SuperSU has been built from the ground up to counter a number of problems with other Superuser access management tools.
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
The discussion and support thread can be found on XDA-Developers here:
http://forum.xda-developers.com/showthread.php?t=1538053
SUPERUSER
This is meant to replace Superuser (if installed), you use either one or the other. You cannot combine them. Statements that this breaks Superuser are therefore completely nonsensical.
NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU.
TRANSLATIONS
Want to help translate SuperSU ? See http://www.getlocalization.com/supersu/ !
UNDELETE FOR ROOT USERS
Description
Undelete for Android is an application for root users that allows you to recover any type of deleted file from your SD card or internal storage.
With support for over 1000 file types, Undelete can come in handy if you accidentally delete photos or want some old tunes to listen to on the go.
Undelete can also securely wipe and shred files so that they will be impossible for others to recover.
Features:
★ Restore any file that has not been written over
★ Securely wipe/shred files
★ Works with documents, images, video, music, archives and binaries
★ Thumbnail preview generation
★ Batch operations
★ Custom restore folder
★ Preview media files
Without the unlock Key, this application will only restore image files. Please buy the Key to unlock full functionality.
Currently, only FAT is supported. On most devices this means that only the external SD is supported.
Some files that are discovered after a scan may fail to recover as the data can be corrupted beyond repair, just like desktop based solutions.
ROOT PERMISSIONS require that you modify the operating system on your device, visit our website for more information: http://fahrbot.co.uk/root
INTERNET and READ DATA permissions are needed for the logging system. Logs are only sent manually with your permission through the "Write to us" dialog.
BUSYBOX
Description
Root required for this application!
The fastest, most trusted, and #1 BusyBox installer and uninstaller!
Over 3 million installs and over 10,000 5 Star ratings!
Mentioned in the new XDA-Developers book "XDA Developers' Android Hacker's Toolkit: The Complete Guide to Rooting, ROMs and Theming"
Winner of best Utility Software award for Android via Handster.
This is the only installer that is ad free and requires no internet permission!
This installer has the smallest Busybox binaries available, right around 800kb unlike the other installers which are over a meg.
The source for this application can be found here: https://code.google.com/p/busybox-android/
Featured on the BusyBox website at: http://busybox.net/products.html
The BusyBox source code can be found here: http://git.busybox.net/busybox/
A must have for any rooted phone! Almost EVERY rooted applications needs BusyBox to perform their magic, if you have a rooted phone then you need BusyBox.
Pro version contains Backup feature (for safer installs), uninstall feature, Advance Smart install feature, the ability to hand pick the applets you want, safety check for missing applets on start, and better overall support. The pro version will receive more frequent updates than the free version will.
Please note I did not write BusyBox! I wrote this installer and cross compiled BusyBox for Android. Please see the about menu option for more details or here: www.BusyBox.net
BusyBox is a software application that provides many standard Unix tools, much like the larger (but more capable) GNU Core Utilities. BusyBox is designed to be a small executable for use with the Linux kernel, which makes it ideal for use with embedded devices. It has been self-dubbed "The Swiss Army Knife of Embedded Linux".
Leave this installed if you always want to get the latest version of busybox!
AnTuTu CPU MASTER (Free)
Description
CPU Master is AnTuTu Free App!
Note: Root is necessary
AnTuTu CPU Master is a tool for changing the CPU/GPU speed on a rooted Android Mobile Phone/Pad.
CPU Master Automatic detection CPU's available frequencys, don't need to manually choose.
CPU Master's OverclockWidget show the CPU and battery stats, and change the CPU speed faster and simple.
Easy to find the following brands HTC,Motorola,Samsung,Google,LG ROOT, CPU Master can set cpu High-low frequency on your rooted mobile, capable of overclock and underclock.
CPU Master feature:
+ Speed up your processor
+ Powersave battery (speed down)
BATTERY CALIBRATION
Description
Calibrate your battery when you think it's miscalibrated.
Requirements: Android 2.1+ | Root permissions
Calibration needs to be done after flashing a new ROM, but you can calibrate any time you think your battery is miscalibrated. This program does it by removing the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.
It's suggested, but not necessary, to let the phone fully discharge after calibration, then charged to 100% without break.
The app shows your actual battery status, and only allows you to start the calibration (i.e. removes the file) when it's fully charged, unless you force earlier calibration.
The voltage meter can be useful too. Full charge is around 4200mV.
There is an option to beep when 100% is reached so you don't have to closley follow the changes.

GL to SD(root)
Description
Root Required.
Get Gameloft games to external SD and work fine.
So you can easily move the game data files to external SD card and solve the problems that internal SD space is too small or slow.It also applies to other games data to external SD, such as gun bros, Dungeon Defenders.
Users can customize the mounted folder in the configuration interface.Must wait for data loading is complete, and set the folder with the corresponding app.It can be used in exceptional folder or navigation, etc.
How to use and please Note:
Only root required.
1.For new user,using "move data" function move your game data to external SD.
(Android/data folder is moved to "data" ,gameloft/games folder is moved to "games",and Android/obb is moved to "obb" folder in the SD card)
2.Run this program.It lists all gameloft games and click 'open' to play.
3.If you wanted see other games (not gameloft)
,press Menu->Click "Setting"->Check "/sdcard/Android"->back to list.
4.If you want to click the desktop icon to execute,You will mount and press Menu -> Exit
5.If you do not know how to move files, delete the /sdcard/gameloft/games data, open wifi, run the program and click game,leave it to download.
6.Press and hold can remove non-game item.
7.If you flashed new rom or updated and "GL to SD" didn't work,please clean the data of "GL to SD".
**Limited to the core of each phone set different, each phone have encountered can not guarantee normal operation.
If not executed, please return your phone's models and ROM versions, have the opportunity to add in the new version.
**When you want to connect to the computer as a USB hard drive, remember to unmount(or check auto unmount).
**There are still some games left running in the background, will mount unsuccessful. Please using other app to kill this game process and re-mount again.
**If you had any question about this app.Email to me.
Suit for:LG P990,P920,Samsung Galaxy Note,Galaxy S2,Galaxy R,i9000,i9003,yp-g1,Galaxy W,YP-G70,Samsung Galaxy Tab(P1000),Acer Iconia A100,Moto Atrix 4G ME860,Photon 4G,razr,Asus Transfomer,Ainol Novo 7
Use but no report:Captivate,SEMC Xperia X10,Table S,Samsung Galaxy Tab,Infuse 4G,Acer Picasso,Moto Droid X2,LG GT540 Optimus,Toshiba Folio 100,Scroll Tablet
(If you have any questions, email me rather than to the star.)
Sixaxis Controller
Description
*** Caution: This app is not for the faint-hearted!! ***
Please read all instructions carefully.
Not all devices are supported, therefore it is strongly recommended that you try the 'Sixaxis Compatibility Checker' (available for free in the Android Market) before purchasing this app.
Finally the wait is over... The ultimate gaming experience awaits! Now you can play games on your phone the way they were meant to be played! Sixaxis Controller allows you to use your Sixaxis and DualShock 3 controllers in many of your favourite games and applications.
*** IMPORTANT ***
- ROOT access is required!!!
- Due to the way pairing is done with the controllers, you need to manually pair your controller with the PC utility 'SixaxisPairTool' (available on the website) and a mini-USB cable. Android 3.1+ users can also pair directly on their devices via USB.
- It is highly recommended that you use an ORIGINAL controller. Many after market controllers will not work with this app. If you get a 'Client connected: 1' message, but the lights on your controller continue to flash, it is almost certainly not an original Sony controller.
- Be sure to read the instructions in the help menu carefully.
Features:
- Up to four Sixaxis and DualShock 3 controllers supported at once.
- Support as a native gamepad in Android 3.1+ devices. Full support for analog sticks and analog triggers.
- Keyboard emulation. Map all buttons and sticks to almost any key available in Android.
- Mouse emulation. Configure a button to activate the mouse pointer on devices that support mice (most tablets, and many phones should work).
- Touch emulation allows you to map buttons and analog sticks to the screen. Play all your favourite games with full analog support, even those without built-in controller support!
This product is not affiliated with, nor authorized, endorsed or licensed in any way by Sony Corporation, its affiliates or subsidiaries. All trademarks are property of their respective holders.
For assistance, full instructions and FAQ, visit our website at http://www.dancingpixelstudios.com
AdFree Android
Description
THIS APP IS FOR ROOTED PHONES ONLY!
AdFree removes most ads in the browser and other apps. It does this by nullifying requests to known host names in the system hosts file.
If you have problems with this app, or you know of additional host names not being filtered, please comment in xda-developers.com forum so it can be fixed!
SD-Booster
Description
SD-Booster speeds up your external and internal SD-Card(s) (external and internal memory) up to 40 times! Enjoy a new feeling of speed on your Android smartphone anytime and everywhere you are.
Starting apps, listing to your favorite music or just swapping data with your PC ? Whatever you do, the SD-Booster improve your phone speed!
SD-Booster needs root permission to run, otherwise SD-Booster can't do anything!
Features:
-MMC detection framework to support any SD-Card
-Speedup every external and internal SD-Card
-Set on Boot
-Color based suggestion terms of current cache size
PLEASE don't move SD-Booster to your SD-Card, otherwise SD-Booster doesn't work on boot!
Script Manager - SManager
Description
Powerful application to execute scripts and executables, root explorer and browser and multi terminal emulator.
Execution Functions:
------------------
Manage and execute shell scripts and programs in file system.
All executions run over vt100 terminal accepting user input and esc codes (colors, bel, cursor movement ..)
Run them at boot-up and on network status change possibility.
Schedule at selected time. (cron jobs)
Show graphical dialogs from running process.
Create widgets at desktop.
Edit and create scripts, also create them from url.
Insert code in your scripts using QR codes.
Share execution output.
Bookmark your scripts.
Test SM_VERSION and/or SM_VERSIONCODE to know if is running inside SManager.
With root privileges you can also execute them with superuser privileges.
File explorer Functions:
------------------------
Browse all phone's file and network files.
Open multiple directories with one screen.(3 directories for Ads version)
Open and edit all files associated to an application.
Click to execute scripts, and long tap to edit, move,copy and rename files and directories. Also Create links and show files properties
Multiselect function from different directories. (Ads version only support 7 selections from different directories. No limit if selections are in the same directory)
With root privileges you can also:
Root explorer
Modify RO (Read Only) partitions easily.
Root editor (Allow edit files with root privileges also usable by other applications. Configure "Browse as root" to use it with script manager or other application)
Open and edit ALL files regardless the permissions they have with selected application. Use CAREFULLY(Configure "Browse as root" in order to get this feature)
Console screen:
---------------
Volume Up: Mapped to Esc key.
Volume Down: Mapped to Enter key.
DPad press: Mapped to Control key. (Press and then press other key. Not simultaneous pressing required)
Enable "extra gestures" in config screen in order to send Home/End,del/tab,left/right,pgup/pgdown keys. This is very useful to execute shell and ssh connections.
WEIRD CHARACTERS: If you get a lot of [[^ characters, is due you have "extra gestures" enabled and script/program doesn't process them. Use most right side of screen to send standard scroll event, or disable "extra gestures"
External Storage SD Notes:
-------------------------
You can install SManager on external Storage SDcard, but you must be know:
- If you are using boot scripts or scheduled script, you will need SMExternalSD app.
- All events like network status change and scheduled scripts while external storage is shared or unmounted will not be processed. Although you have SMExternalSD installed
NOTE:
SManager does not launch executions until external storage is mounted.
NOTE2:
Detected some programs/daemons (like dropbear) fails if has stdin closed. Try put "exec 0>&1" to reopen stdin in background executions.
No ads version features:
------------------------
No ads.
Execute scripts from widgets without opening console.
No limits in multiselect.
No limits opening multiple directories.
Alias keys in SMConsole.
Hide/show SMConsole status bar with up/down gesture at top of SMConsole screen.
FasterFix
Description
Speed up your gps, and get faster GPS-Fixes using FasterFix.
- Root access required -
- BusyBox Required -
- New HTC phones need NAND-unlock -
This app enhances your GPS by using a more accurate time estimation from a NTP server near you. Select one from the list, or add your own.
If the app doesn't work, please use "root checker" to check if you are correctly rooted and busybox is installed before you give a bad rating.

reserved 2

reserved 3 now u can post

nice thread

updated nov 03 with script manager and faster fix

MPEngine™(new RPEngine™update!) "Designed for Hardcore Gamers

MPEngine™(new RPEngine™update!) "Designed for Hardcore Gamers
First of all this is not my work and i am just sharing..
you can find original thread here
What does it do?
-MPEngine is a live engine script which was supposed to help on some parts that LazerDroid script couldn't handle,
but now its complete independent script(some little parts are shared), this one beast engine will demolish all those crappy huge lags
How to apply to our pico...?
1.first download busybox
2.download the latest flashable zip in attachments, flash through recovery.
3.reboot & enjoy!
How to check if it works?
for RPEngine12.
-open terminal shell
-type cat /proc/sys/vm/drop_caches.
-if the result is 3, it means its working!
if you have problem that the script doesnt get applied, try manually extracting files and copy those files into the right position.
-/rpengine/ should be pasted to your /system/rpengine/
-/etc/ should be pasted to your /system/etc/
-/xbin/ should be pasted to your /system/xbin/
1.how does it work?
this engine is made to clear out all lags that happens while playing high end games on your inefficient ram memory.(512mb or less)
tuning LMKs will tend to freeup more memory, so many of you think just tuning this will kill all the lags on games.
well then how about gta3 or max payne games? do they work better?
afaik, LMKs kill processes but the leftovers(registered caches) still remain.
the free ramspace youre seeing through task manager is not entirely a freememory.
so even though LMK cleans all the processes, games will suffer from lags because they have to detect which cache remains and which cache gets dumped.
this engine calculates all that sh*t and flushes page caches REALTIME. once you apply this and play a game, you will notice that there is no more hanging on gta3 or max payne games.
some of you may have a question about why this cache doesnt drop dentries and inodes.
its because clearing inodes will make apps totally lose control and have to rebuild it again, what a resource waste. also apps will still be able to load faster since inodes and dentries remain.
page cache normally takes up bigger amount of ram than dentries or inodes. so why you want to drop all caches? dropping only page cache is more efficient than ever!
2.advantages of tuning usrsettings
this version has a cool feature called usrsettings.
changing values for this file will immediately take affect, you dont have to reboot(except VALUE11 & VALUE14).
the default settings were based on my crappy and sluggish radiowave walkie-talkie, so manually tuning them for your own device may give you much more advantages.
3.how to use usrsettings.
there is a file called usrsettings on the same directory. open with text editor, and edit.the descriptions about which value does sth is included in there also. good luck!
(some engine parts were disabled by default like dalvik booster, but these settings can be re-enabled by editing usrsettings. oh, and some easter eggs are hidden in there
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Press thanks if that works

shree15 said:
MPEngine™(new RPEngine™update!) "Designed for Hardcore Gamers
First of all this is not my work and i am just sharing..
you can find original thread here
What does it do?
-MPEngine is a live engine script which was supposed to help on some parts that LazerDroid script couldn't handle,
but now its complete independent script(some little parts are shared), this one beast engine will demolish all those crappy huge lags
How to apply to our pico...?
1.first download busybox
2.download the latest flashable zip in attachments, flash through recovery.
3.reboot & enjoy!
How to check if it works?
for RPEngine12.
-open terminal shell
-type cat /proc/sys/vm/drop_caches.
-if the result is 3, it means its working!
if you have problem that the script doesnt get applied, try manually extracting files and copy those files into the right position.
-/rpengine/ should be pasted to your /system/rpengine/
-/etc/ should be pasted to your /system/etc/
-/xbin/ should be pasted to your /system/xbin/
1.how does it work?
this engine is made to clear out all lags that happens while playing high end games on your inefficient ram memory.(512mb or less)
tuning LMKs will tend to freeup more memory, so many of you think just tuning this will kill all the lags on games.
well then how about gta3 or max payne games? do they work better?
afaik, LMKs kill processes but the leftovers(registered caches) still remain.
the free ramspace youre seeing through task manager is not entirely a freememory.
so even though LMK cleans all the processes, games will suffer from lags because they have to detect which cache remains and which cache gets dumped.
this engine calculates all that sh*t and flushes page caches REALTIME. once you apply this and play a game, you will notice that there is no more hanging on gta3 or max payne games.
some of you may have a question about why this cache doesnt drop dentries and inodes.
its because clearing inodes will make apps totally lose control and have to rebuild it again, what a resource waste. also apps will still be able to load faster since inodes and dentries remain.
page cache normally takes up bigger amount of ram than dentries or inodes. so why you want to drop all caches? dropping only page cache is more efficient than ever!
2.advantages of tuning usrsettings
this version has a cool feature called usrsettings.
changing values for this file will immediately take affect, you dont have to reboot(except VALUE11 & VALUE14).
the default settings were based on my crappy and sluggish radiowave walkie-talkie, so manually tuning them for your own device may give you much more advantages.
3.how to use usrsettings.
there is a file called usrsettings on the same directory. open with text editor, and edit.the descriptions about which value does sth is included in there also. good luck!
(some engine parts were disabled by default like dalvik booster, but these settings can be re-enabled by editing usrsettings. oh, and some easter eggs are hidden in there
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Press thanks if that works
Click to expand...
Click to collapse
I have flashed it over stock Rom but nothing happened , for your satisfaction I have attached a screenshot also , u may check it .
Regards
Via HTC Sense

{
"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"
}
Via HTC Sense

Use on cm 10.1. ROM started lagging. Tr 2 was a game full of lags.
Sent from my HTC Explorer A310e using xda premium

Flashed on CM9 #11 end with bootloop
Sent from my HTC Explorer using xda premium

Working on Sense 4 build #6
Blue3125 said:
I have flashed it over stock Rom but nothing happened , for your satisfaction I have attached a screenshot also , u may check it .
Regards
Via HTC Sense
Click to expand...
Click to collapse
Its working for me on Sense 4 #6.. it doesn't get applies on automatically though.. i had to apply it manually..and my lagging game stopped lagging so that why i posted.but if it doesn't worked for you then sorry for trouble..

shree15 said:
Its working for me on Sense 4 #6.. it doesn't get applies on automatically though.. i had to apply it manually..and my lagging game stopped lagging so that why i posted.but if it doesn't worked for you then sorry for trouble..
Click to expand...
Click to collapse
Just rebooted thrice and I saw that now it shows 1 rather than 0 in terminal emulator.
Regards
Via HTC Sense

shree15 said:
MPEngine™(new RPEngine™update!) "Designed for Hardcore Gamers
First of all this is not my work and i am just sharing..
you can find original thread here
What does it do?
-MPEngine is a live engine script which was supposed to help on some parts that LazerDroid script couldn't handle,
but now its complete independent script(some little parts are shared), this one beast engine will demolish all those crappy huge lags
How to apply to our pico...?
1.first download busybox
2.download the latest flashable zip in attachments, flash through recovery.
3.reboot & enjoy!
How to check if it works?
for RPEngine12.
-open terminal shell
-type cat /proc/sys/vm/drop_caches.
-if the result is 3, it means its working!
if you have problem that the script doesnt get applied, try manually extracting files and copy those files into the right position.
-/rpengine/ should be pasted to your /system/rpengine/
-/etc/ should be pasted to your /system/etc/
-/xbin/ should be pasted to your /system/xbin/
1.how does it work?
this engine is made to clear out all lags that happens while playing high end games on your inefficient ram memory.(512mb or less)
tuning LMKs will tend to freeup more memory, so many of you think just tuning this will kill all the lags on games.
well then how about gta3 or max payne games? do they work better?
afaik, LMKs kill processes but the leftovers(registered caches) still remain.
the free ramspace youre seeing through task manager is not entirely a freememory.
so even though LMK cleans all the processes, games will suffer from lags because they have to detect which cache remains and which cache gets dumped.
this engine calculates all that sh*t and flushes page caches REALTIME. once you apply this and play a game, you will notice that there is no more hanging on gta3 or max payne games.
some of you may have a question about why this cache doesnt drop dentries and inodes.
its because clearing inodes will make apps totally lose control and have to rebuild it again, what a resource waste. also apps will still be able to load faster since inodes and dentries remain.
page cache normally takes up bigger amount of ram than dentries or inodes. so why you want to drop all caches? dropping only page cache is more efficient than ever!
2.advantages of tuning usrsettings
this version has a cool feature called usrsettings.
changing values for this file will immediately take affect, you dont have to reboot(except VALUE11 & VALUE14).
the default settings were based on my crappy and sluggish radiowave walkie-talkie, so manually tuning them for your own device may give you much more advantages.
3.how to use usrsettings.
there is a file called usrsettings on the same directory. open with text editor, and edit.the descriptions about which value does sth is included in there also. good luck!
(some engine parts were disabled by default like dalvik booster, but these settings can be re-enabled by editing usrsettings. oh, and some easter eggs are hidden in there
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Press thanks if that works
Click to expand...
Click to collapse
Failed
I had to reflash my rom
Sent from my HTC Explorer A310e using xda premium

Ppl who are trying to flash it.. don't.. doesn't always work.. just extract it and place the files in appropriate folders.. run it with Script Manager.. reboot!
I've been using all its updates since 2 months.. always works fine for me! No bootloops ever..!:beer:

Dropping caches so repeatedly will hurt your performance.

So what does that mean ?
Blue3125 said:
Just rebooted thrice and I saw that now it shows 1 rather than 0 in terminal emulator.
Regards
Via HTC Sense
Click to expand...
Click to collapse
Does that means the script is working ? Cause I am on sense 4 too and terminal emulator shows 1

Araib93 said:
Does that means the script is working ? Cause I am on sense 4 too and terminal emulator shows 1
Click to expand...
Click to collapse
I'm still confused about it :/
Via HTC Sense

How to install it ??? I am on stock Rom
Sent from my HTC Explorer A310e

is it working or not guys?

ferbus said:
is it working or not guys?
Click to expand...
Click to collapse
No it dosnt
via HTC Sense

Then y the hell is this thread open
Coz this is working for no one
Not working on any rom
Bhla bhla bhla bhla !!!!!
Sent from my HTC Explorer using xda premium

[Guide+Tweaks+Mods+Scripts+Apps] (Make Most Of Your Phone Ram And Processor) UPDATED

All Tweaks And Mods Are Not Devloped By Me So The Creadit Goes To The Devlopers....
Warning:-All These Tweaks And Mods Are Tested But Try On Your Own Risk....
Make A Backup Of Your Rom Before Trying Anything...
(•1) Get more RAM and faster responses by disabling verify-bytecode!
AS WITH ANY MODDING PROCEDURE FOR YOUR PHONE, THIS GUIDE ALSO COMES WITH NO WARRANTY. I HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF FOLLOWING THIS GUIDE. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING.
This is not useful in odexed ROMs & devices with 1GB or more RAM. However, this will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=v
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
2) Add these to the /data/local.prop or build.prop.
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=v
(Copy local.prop or build.prop to SD and edit them. Copy back afterwards. If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already, please modify them as above. Also type following in adb shell or terminal emulator.
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
Advantages:More free RAM.
Faster launch for system & user apps during the second launch.
Gives as much as of a performance boost as ODEX without odexing. Themer friendly.
Smoother app switching.
Disadvantages:Might break some apps.
(•2) Seeder 2.0.0 entropy generator to provide significant lag reduction
Use Seeder For Lag Reduction
Here:- http://forum.xda-developers.com/showthread.php?t=1987032
(•3) One click ODEXing a ROM for more RAM and better speed
Here's an alternative way to gain more RAM and performance without odexing.
Get more RAM and faster responses by disabling verify-bytecode!
This process will usually give just as much as performance boost as odexing SYSTEM and USER app.
AS WITH ANY MODDING PROCEDURE/SCRIPTS FOR YOUR PHONE, THIS SCIPT ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF RUNNING THIS SCRIPT. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING. MAKE SURE YOU HAVE AT LEAST 15% FREE ON /SYSTEM, THIS IS IMPORTANT BECAUSE IF YOU RUN OUT OF SPACE THINGS WILL GO BADLY WRONG..
Requires busybox.
If your system partition is almost full, have a look at http://forum.xda-developers.com/showthread.php?t=734236.
This script will *attempt* to odex all apks found at /system/app. Theming would be impossible once the ROM is odexed. Themes applied at the time of odexing will be preserved. If you plan on applying a theme, apply it before odexing. If you want to theme after odexing, you must deodex the ROM before theming. If you change themes often, odexing is not for you.
Quick Instructions for Windows:
Connect the phone with USB cable and enable USB debugging. (No wireless or Android Terminal shell)
Put the phone in airplane mode.
Download and extract the attached file and run odex.bat
Instructions for advanced users:
This attachment contains a folder called odex. Push that folder to data and set the permission of odex.sh to 4755. Mount system as r/w(could be done via adb remount system). Next, execute odex.sh. All of this should be done via USB using ADB shell. Do not use wireless adb or Android Terminal.
Advantages:
More free space in system partition.
Faster booting.
More free RAM(I was able to gain 20-30MB.)
Faster access to system apps.
Disadvantages:
Cannot be themed after odexing.
APK tweaks cannot be applied.
Might break some of the non-AOSP system apps such as Root Explorer if they are installed as system app.
Acknowledgments:
Only the odex.bat was created by me. Similar projects were done in past but most of the downloads are broken. So, I collected together different stuff from different places to put together this package.
adb.exe is from the RATC batch ROOT.
adb dlls are from Android SDK
odex.sh is from Paul O Brian from MoDaCo (pastebin.com/EZLWUdea)
zip, zipalign and dexopt-wrapper are from XDA (http://forum.xda-developers.com/showthread.php?t=734236)
(•4) V6 SuperCharger +DIE-HARD Launcher
This One Is The Beat And I Think Nothing Can Beat It Takes Your Phone Flying....
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
Here Is The Link:- http://forum.xda-developers.com/showthread.php?t=991276
(•5) Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock {CROSSBREESER}
What CrossBreeder Does....
1. It's a big new feature, removal of DNS lag . A lot of the lag in a lot of apps, apart from the GUI lag, is due to slow DNS querying, specially on the mobile network.
CrossBreeder now runs a caching, parallelising DNS client on the device. So now most of your DNS queries will be served from the cache and if not found, the query will be sent in in round robin fashion to multiple DNS servers including Google DNS, OpenDNS and your home router and the reply will be served to you, hot.
This speeds up network access and networked apps, like Browsers of course, and Tapatalk, Gmail and thousands of others drastically. And removes a lot of the lag where it was due to DNS querying. This will not increase your network or download speed but pages will load much faster.
This will future proof your devices as more and more apps start using HTML5 and/or reside completely as web pages or the like.
CrossBreeder now boosts your tethering connection. Client devices to your device will take advantage of the new DNS. Hence their usage is also improved! In many cases this update might even fix a broken tethering feature on your phone. So if your ROM doesn't have a working tethering support, you an try and install this update. It might magically start working!
Here Is The Link With Description:- http://forum.xda-developers.com/showthread.php?t=2113150
(•6)Apps For Tweaks And All
Pimp My ROM - The only app that implements tweaks I can't do on my own and applies them well if you take the time to apply the right tweaks. You'll learn about PMR tweaks later.
Quadrant/Nenamark2 - Standard benchmarking and stress testing.
Android Tuner Pro - I don't apply any tweaks through AT, in fact I have most of ATs features disabled or hidden (my favourite aspect of AT is its customizability). However, this is the app I use most frequently throughout the tweaking and testing process. AT has incredible system monitoring features. AT allows me to actually collect data so I can objectively measure a tweaks impact on performance. It also has a great root terminal shell and script manager.
AntTek Explorer- Root file manager that is great for managing scripts. Has a built in text editor, great customizable UI, low footprint, and makes the process of enabling init.d scripts easier than other file managers. It also reminds me of nautilus and other linux file managers, which is a wonderful thing.
SDMaid Pro- Great for system cleaning and app management. During testing, whether deliberately or unintentionally, I crash my system a lot (my cpu hates me). SDMaid allows me to clean up junk system files after crashes. On average a system crash generates a couple mb of junk files (logs, etc) that I have no use for. SDMaid also clears app caches without clearing any settings or other data. I know your not supposed clear caches all the time but after all the crashes I put my system through during testing it is useful every once in a while.
LagFix Premium - Another app thats great for maintaining sdcard performance if your constantly wiping, restoring, and flashing.
And If You Are Newbie Try To Understand It.
I Will Be Updating This Topics For Future.....
If You Like It Hit The Thanks Button
Any Ideas And Request Would Be Great....
And Pls Reply Don't Quote....

Re: [Guide] (How To Make Most Of Your Phone Ram And Cpu)
Pls Post Suggestions And Ideas To Keep This Thread Updated....
Sent from my LG-E400 using xda premium

Re: [Guide] (How To Make Most Of Your Phone Ram And Cpu)
You should add the Crossbreeder script here
Sent from my A9 using Tapatalk 2

Perfomace apps for rooted devices

[email protected]@T:
Hi guyz today im gonna discuss about top apps which increses perfomance or are helful in any other way on rooted devices only.
1 >Greenify
Greenify is an Android app that can improve your device's battery life and performance by hibernating certain apps.
2>SEEDER
Many people might not be aware of this app.This app reduces the lag which every one of you might have experienced while switching between apps.I personally have experienced this app and it actually does remove lags.
3> XPOSED INSTALLER
Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo. As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations.
4> SET CPU
SetCPU is a tool for changing the CPU settings on a rooted Android phone or tablet. SetCPU works with a great variety of Android devices and ROMs, including the HTC One series, Samsung Galaxy series, and Nexus devices. You're under control: SetCPU can improve your performance, save battery, or both!
Automate SetCPU with profiles! SetCPU allows you to set up powerful profiles to change your settings under certain conditions, such as what app is running, when the phone is asleep or charging, when the battery level drops below a certain point, when the phone's temperature is too high, or during certain times of day. See the screenshots for examples of how you might set up profiles.
SetCPU's wide feature set make it useful to Android beginners and enthusiasts alike. Accelerate yo...
5> CHAINFIRE 3D
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins too.
6> NO-FRILLS CPU
No-frills CPU Control is a tool you can use on your Android phone to quickly set the CPU frequencies and governor to use. It allows you to use the highest frequency your phone supports and gain some precious FPS in your preferred game, or go down to the lowest frequency and gain some more juice when your phone is sitting idle. All of this without any memory footprint or services running in the background!
8> TITANIUM BACKUP
Titanium Backup is a backup utility for Android that backs up your system and user applications along with their data on external storage of your choice. It is a leading Android application that uses root access to pull all your important applications and data from the system partition and stores them for future restoration. Whether your phone is corrupted or flashed with a custom ROM, Titanium Backup can save the hassle to get your phone loaded up just like it was before. Best of all, it is FREE! If you use it regularly, the PRO version will enhance the experience like never before! Get it today and protect your precious data before its too late!
9> ROOT APP DELETE
best tool for android users, and works better with root permission.
it helps you easily and quickly manager system apps (freeze or remove), the best tool for managing your android system.
compared to other clean or uninstall tools, it is much more better and special:
* tiny,fast, even running on old phones with low memory.
* "modify" MODE, change system apps before uninstalling
* can "Disable" backgroud system service, such as "google backgroud transport" and "contact sync service"
I have personally used all the apps and I think they are very good.
Sent from my Micromax a110 using XDA Free mobile app

Where can I get that Seeder app? Thanks.
Sent from my SM-N910C using XDA Free mobile app