[MOD][JB] Super Launcher + Slimmer + SQLite Optimization [ALL ROMs]
Introduction:
I was searching for ways to keep the android home launcher in memory like many applications have options when I stumbled over this MOD. This thread is to provide Super Strength Launcher+ other MODs for multiple Jelly Bean ROMs out there that suffer from Launcher redraws, Micro lags in the UI etc. due to the low RAM constraints on the GT-i9000.
Basically it is the Launcher that makes a big difference in the overall smoothness of the ROM. There was a build.prop tweak in ROMs up till GB that helped make the HOME launcher stay in memory no matter how much free RAM was available as below
Code:
ro.HOME_APP_ADJ=1
The problem with ICS/JB ROMs is that these don't read the ADJ values from build.prop or local.prop as they are hard-coded into the services.jar!
So I patched the services.jar file to change the OOM priorities which gave me Super Launcher and other UI improvements.
PS: THIS MOD IS FOR Galaxy S GT - I9000.
PS: THIS MOD IS NOT DEPENDENT ON THE LAUNCHER. IT WORKS FOR ANY LAUNCHER SET AS THE DEFAULT.
Details:
This MOD is a collection of tweaks to the services.jar file taken from the Supercharger MOD by zeppelinrox additionally with some added build.prop and GPU acceleration tweaks. The collection of tweaks will grow in the future as I update this thread. If you are using The supercharger script then there wont be much performance gain with this tweak. THE SUPERLAUNCHER DOES NOT GET KILLED BY LONG PRESSING BACK BUTTON
The SQLite optimization script was taken from pikachu01 from the well known Thunderbolt script pack. This optimizes the APP databases, hence boosting the app data access and app response times.
Testing:
This mod was tested by me, personally on my daily driver Galaxy S GT-i9000 along with the stock/semaphore kernels and gave excellent results with nearly no launcher redraws at all. The details of the changes in the priorities are provided in the third post.
Note: DO THIS AT YOUR OWN RISK. MAKE A NANDROID BACKUP AS A PRECAUTION. IF ANYTHING GOES WRONG REFLASH YOUR ROM.
Reboot will take longer than usual due to rebuilding of the optimized dalvik-cache.
Updates:
I will try to maintain the thread with regular updates concentrating on the CM10 releases (CM10 user, personally the best out there ) and others according to my ability to personally test them. Downloads in following post.
Additional Info:
If you want to Apply Super to any other App read this. If you want me to get you this MOD for any other ROM. PM me with the services.jar file from framework attached along with the ROM name. I will add it here.
If you do not suffer from severe launcher redraws and UI lag issues, do no flash this MOD.
If you do not find any improvements at all then you are probably doing something wrong or it is not applicable to your specific device or your specific requirements. PLEASE DO NOT START FLAMING
OK... Here's what I use on a daily basis. And I cannot express the smoothness...Butter pure Butter...!
Currently I am running everything in GPU configuration...! testing... and its smooth believe me... it is...
The system tries to pre-verify all classes in a DEX file to reduce class load overhead, and performs a series of optimizations to improve runtime performance. Both of these are done by the dexopt command, either in the build system or by the installer. On a development device, dexopt may be run the first time a DEX file is used and whenever it or one of its dependencies is updated ("just-in-time" optimization and verification).
There are two command-line flags that control the just-in-time verification and optimization, -Xverify and -Xdexopt. The Android framework configures these based on the dalvik.vm.verify-bytecode property.
If you set:
Code:
adb shell setprop dalvik.vm.verify-bytecode true
then the framework will pass -Xverify:all -Xdexopt:verified to the VM. This enables verification, and only optimizes classes that successfully verified. This is the safest setting, and is the default.
If dalvik.vm.verify-bytecode is set to false, the framework passes -Xverify:none -Xdexopt:verified to disable verification. (We could pass in -Xdexopt:all, but that wouldn't necessarily optimize more of the code, since classes that fail verification may well be skipped by the optimizer for the same reasons.) Classes will not be verified by dexopt, and unverified code will be loaded and executed.
Enabling verification will make the dexopt command take significantly longer, because the verification process is fairly slow. Once the verified and optimized DEX files have been prepared, verification incurs no additional overhead except when loading classes that failed to pre-verify.
If your DEX files are processed with verification disabled, and you later turn the verifier on, application loading will be noticeably slower (perhaps 40% or more) as classes are verified on first use.
For best results you should force a re-dexopt of all DEX files when this property changes.
Execution Mode
The current implementation of the Dalvik VM includes three distinct interpreter cores. These are referred to as "fast", "portable", and "debug". The "fast" interpreter is optimized for the current platform, and might consist of hand-optimized assembly routines. In constrast, the "portable" interpreter is written in C and expected to run on a broad range of platforms. The "debug" interpreter is a variant of "portable" that includes support for profiling and single-stepping.
The VM allows you to choose between "fast" and "portable" with an extended form of the -Xint argument. The value of this argument can be set through the dalvik.vm.execution-mode system property.
To select the "portable" interpreter, you would use:
If the property is not specified, the most appropriate interpreter will be selected automatically. At some point this mechanism may allow selection of other modes, such as JIT compilation.
Not all platforms have an optimized implementation. In such cases, the "fast" interpreter is generated as a series of C stubs, and the result will be slower than the "portable" version. (When we have optimized versions for all popular architectures the naming convention will be more accurate.)
I know this is an i9000 thread, but.... I am on slim bean 2.1 and have an i897(captivate) are the modifications done in Slim 2.1 BulletProof device specific or is this something that will work on any device running slim bean?
***edit***examining the package it seems to have some updates to build prop that refer to i9000, does this mean I can't use it? If not; If I gave you my build prop would you mind doing the same for the i897?
I know this is an i9000 thread, but.... I am on slim bean 2.1 and have an i897(captivate) are the modifications done in Slim 2.1 BulletProof device specific or is this something that will work on any device running slim bean?
***edit***examining the package it seems to have some updates to build prop that refer to i9000, does this mean I can't use it? If not; If I gave you my build prop would you mind doing the same for the i897?
Just pm me the services.jar file from framework folder and the build.prop file... will make a package and add here for everyone.
Getting feedback for your app during development is as simple as adding logging info where necessary and looking … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
[MOD][JB] Super Launcher + Slimmer + SQLite Optimization [ALL ROMs]
Print
Email
THREAD CLOSED
[MOD][JB] Super Launcher + Slimmer + SQLite Optimization [ALL ROMs]
) and others according to my ability to personally test them. Downloads in following post. 
View Profile
Visit Homepage
View Forum Posts
View GitHub profile
Downloads
Follow your feelings
Clicking in "thanks" button doesn´t hurt. Try it!
View Facebook page
THREAD CLOSED
Linear Mode
