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.
Requirements:
specified ROM
Recovery
Basic flashing knowledge
Installation:
Download
Reboot to recovery
Flash ZIP
Advanced -> Wipe dalvik-cache [Absolutely Necessary]
Optionally flash the Slimmer package.
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. :fingers-crossed:
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
Credits:
zeppelinrox
Android Dalvik VM
Supercharger
Windows Auto Patcher
pawitp
krarvind
stratosk
OOM Priorities
Configuring internal process priorities
Android Internal System Task Killer
Please do say thanks to zeppelinrox. [link above]
And LOL watching the below video...
Downloads
If you find improvements then show your support by buying me a drink and/or clicking the thanks button
Also thank zeppelinrox for the OOM Priorities..
FLASHING SL + SQLITE OPTIMIZER AFTER THE WHOLE ROM IS SET UP WILL MAKE THE BIGGEST DIFFERENCE.!!!
Please Do Mount the Partitions in Recovery or the File May not be Flashed.!
Change Log:
1222 : Updated ROM Slimmer
1213 : Fixed mounts points for SQLite script. [thanks StuttgartKiwi]
1117 : Fixed Progress Bar
1005 : Optimizing SQLite DB! [Faster App DB Access]
924 : VM Heap Size 96MB [Found to be better ...][Reverted!]
91X : Touchscreen Enhancements! [Testing...]
830 : Performance Boost on the Way...! Absolute Butter...!
829 : Launcher priority changes = not visible in running apps.
SQLite Optimizer + [Faster App DB Access] Click Here.!
Smaller ROM == Faster Xperience...? ROM Slimmer v1.2
Gets rid of the following...
Code:
Apollo
CMWallpapers RomManager
DSPManager Stk
Email Talkback
Exchange2 Term
GoogleFeedback File Manager[Not CM]
Galaxy4 VideoEditor
GenieWidget VpnDialogs
Gmail GoogleEars
HoloSpiralWallpaper FaceLock
HTMLViewer Bootanimation
Launcher2 Music[and FX]
MagicSmokeWallpapers lang_pico [all except en_*]
NoiseField media/video
PicoTTS Offline charging animation
Modify the updater-script to add/remove entries.
Want Mod for a ROM. Post the Services.jar and Build.prop for the ROM.
Downloads:
CyanogenMod 10.1
CM10.1 0319 NIGHTLY
CM10.1 0304 EXPERIMENTAL M2
CM10.1 0121 EXPERIMENTAL M1
OLDER BUILDS...?
CM10.1 0312 NIGHTLY
CM10.1 0210 NIGHTLY
CM10.1 0130 NIGHTLY
CM10.1 0123 NIGHTLY
CM10.1 0122 NIGHTLY
CM10.1 0119 NIGHTLY
CM10.1 0117 NIGHTLY
CM10.1 0113 NIGHTLY
CM10.1 0111 NIGHTLY
CM10.1 0110 NIGHTLY
CM10.1 0108 NIGHTLY
CM10.1 0105 NIGHTLY
CM10.1 0104 NIGHTLY
CM10.1 0103 NIGHTLY
CM10.1 1231 NIGHTLY
CM10.1 1230 NIGHTLY
CM10.1 1228 NIGHTLY
CM10.1 1226 NIGHTLY
CM10.1 1223 NIGHTLY
CM10.1 1222 NIGHTLY
CM10.1 1221 NIGHTLY
CM10.1 1220 NIGHTLY
CM10.1 1219 NIGHTLY
CM10.1 1217 NIGHTLY
CM10.1 1214 NIGHTLY
CM10.1 1213 NIGHTLY
Slim Bean 4.2.2
Slim Bean 4.2.2 Build 3 [I9000]
OLDER BUILDS...?
Slim Bean 4.2.2 Build 2 [I9000]
Slim Bean 4.2.2 Build 1 [I9000]
Slim Bean 4.2.1 Stable 1.0 [I9000]
Slim Bean 4.2.1 RC 2 [I9100G]
Slim Bean 4.2.1 RC 2 [N7100]
Slim Bean 4.2.1 RC 2 [I9100G]
Slim Bean 4.2.1 RC 2 [N7100]
Slim Bean 4.2.1 RC 2 [I9000]
Slim Bean 4.2.1 RC 1 [I9000]
Slim Bean 4.2.1 RC 1 [I9100G]
Slim Bean 4.2.1 Beta 2 [I9000]
Slim Bean 4.2.1 Beta 2 [I9100G]
Slim Bean 4.2.1 Beta 1 [I9000]
Slim Bean 4.2.1 Beta 1 [I9100G]
CyanogenMod 10
CM10 1215 NIGHTLY
CM10 STABLE
OLDER BUILDS...?
CM10 1214 NIGHTLY
CM10 1210 NIGHTLY
CM10 1201 NIGHTLY
CM10 1126 NIGHTLY
CM10 1124 NIGHTLY
CM10 1123 NIGHTLY
CM10 1121 NIGHTLY
CM10 1120 NIGHTLY
CM10 1119 NIGHTLY
CM10 1118 NIGHTLY
CM10 1117 NIGHTLY
CM10 1116 NIGHTLY
CM10 1115 NIGHTLY
CM10 1114 NIGHTLY
CM10 1112 NIGHTLY
CM10 1111 NIGHTLY
CM10 1109 NIGHTLY
CM10 1108 NIGHTLY
CM10 1107 NIGHTLY
CM10 1106 NIGHTLY
CM10 1104 NIGHTLY
CM10 1103 NIGHTLY
CM10 1102 NIGHTLY
CM10 1101 NIGHTLY
CM10 1031 NIGHTLY
CM10 1030 NIGHTLY
CM10 1029 NIGHTLY
CM10 1027 NIGHTLY
CM10 1026 NIGHTLY
CM10 1024 NIGHTLY
CM10 1023 NIGHTLY
CM10 1022 NIGHTLY
CM10 1021 NIGHTLY
CM10 1017 NIGHTLY
CM10 1014 NIGHTLY
CM10 1013 NIGHTLY
CM10 1012 NIGHTLY
CM10 1011 NIGHTLY
CM10 1011 EXPERIMENTAL M2
CM10 1010 NIGHTLY
CM10 1008 EXPERIMENTAL EXPERIMENTAL BUILD!
CM10 1008 NIGHTLY DO NOT FLASH ON EXP BUILD!
CM10 1003 NIGHTLY
CM10 1006 NIGHTLY
CM10 1005 NIGHTLY
CM10 1004 NIGHTLY [FISHEARS BUILD]
CM10 1002 NIGHTLY
CM10 1001 NIGHTLY [1001 NIGHTS. LOL ]
CM10 930 NIGHTLY
CM10 929 NIGHTLY
CM10 928 NIGHTLY
CM10 927 NIGHTLY
CM10 926 NIGHTLY [New Layout!]
CM10 925 NIGHTLY [EXPERIMENTAL!]
CM10 924 NIGHTLY
CM10 923 NIGHTLY
CM10 920 NIGHTLY
CM10 919 NIGHTLY Choppy? Read This!
CM10 918 NIGHTLY Choppy? Read This!
CM10 917 NIGHTLY Choppy? Read This!
CM10 914 NIGHTLY
CM10 913 NIGHTLY
CM10 912 NIGHTLY
CM10 910 NIGHTLY
CM10 908 NIGHTLY
CM10 907 NIGHTLY
CM10 906 NIGHTLY
CM10 905 NIGHTLY
CM10 904 NIGHTLY
CM10 902 NIGHTLY [903]
CM10 901 NIGHTLY [902]
CM10 901 NIGHTLY
CM10 831 NIGHTLY
CM10 830 NIGHTLY [Full GPU Rendering from this build and above.]
CM10 829 NIGHTLY
CM10 828 NIGHTLY
CM10 827 NIGHTLY
CM10 826 NIGHTLY
CM10 825 NIGHTLY
CM10 824 NIGHTLY
CM10 823 NIGHTLY
CyanogenMod 9
CM9 916 NIGHTLY
CM9 909 NIGHTLY
CM9.1.0 Stable
Slim Bean
Slim Bean 3.1
Slim Bean 3.1 [I9100G]
OLDER BUILDS...?
Slim Bean 3.0
Slim Bean 3.0 [I9100G]
Slim Bean 2.9
Slim Bean 2.8
Slim Bean 2.7
Slim Bean 2.6
Slim Bean 2.5
Slim Bean 2.4
Slim Bean 2.3
Slim Bean 2.2
Slim Bean 2.1 Update 1
Slim Bean 2.1 [Captivate]
Slim Bean 2.0/2.0.1
HellyBean
HellyBean 0105 I9000 [4.2.1]
HellyBean 1231 I9000 [4.2.1]
OLDER BUILDS?
HellyBean 1228 I9000 [4.2.1]
HellyBean 1224 I9000 [4.2.1]
HellyBean 1115 Captivate
HellyBean 1030 I9000
HellyBean 1030 Captivate
HellyBean 1023 I9000
HellyBean 1023 Captivate
HellyBean 1018 I9000
HellyBean 1017 I9000
HellyBean 1014 I9000
HellyBean 1014 Captivate
HellyBean 1012 I9000
HellyBean 1012 Captivate
HellyBean 1012 I9000
HellyBean 1010 I9000
HellyBean 1010 Captivate
HellyBean 1007 Captivate
HellyBean 1007 I9000
HellyBean 1001 I9000
HellyBean 927 I9000
HellyBean 925 I9000
HellyBean 921 I9000
HellyBean 920 I9000
HellyBean 919 I9000
HellyBean 917 I9000
HellyBean 911 I9000
HellyBean 909 I9000
HellyBean 908 I9000
HellyBean 904 I9000
HellyBean 901 I9000
HellyBean 830 I9000
HellyBean 828 I9000
HellyBean 820 I9000
HellyBean 820 Captivate
HellyBean 820 Fascinate
HellyBean 820 Vibrant
AOKP JB
AOKP Milestone 1
AOKP Milestone 1 [Fascinate]
Older Builds?
AOKP Build 5
AOKP Build 4 [Fascinate]
AOKP Build 4
AOKP Build 3
AOKP Build 2
AOKP 829 Build
AOKP 826 Build
ELITE
ELITE RC 13
ELITE RC 12.1
OLDER BUILDS...?
ELITE RC 12
ELITE RC 11
Paranoid Android
PA v2.54
PA v2.52
OLDER BUILDS...?
PA v2.51
PA v2.23
PA v2.22
PA v2.20
PA v2.16
PA v2.15
PA v2.12
PA v2.10 [New Layout]
PA v1.991 [New Layout]
PA v1.99 [Old Layout]
CodeNameAndroid
CNA v3.3.1
LANIGHT
LANIGHT v8.0
X-Bean
X-Bean 3.0
X-Bean 2.0
OLDER BUILDS?
X-Bean v1.1 Pre?
X-Bean v1.0
TiramiSlim
TiramiSlim 2.0 [Test!]
Eclipse
Eclipse 2.1 Build 4
CREED
CREED v9
CREED v8
Slow Boot Up:
Read This
Configuration:
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...
Slim Bean Latest
Semaphore Latest
1140 MHz
Ondemand/Interactive
No-op/SIO
Bigmem
512 kB read ahead
Sensitive Touchscreen
Patched JB Hugemem Libs
ROM Slimmer
Super Launcher+ Mod
Inverted Apps + Framework
Changes:
Bytecode Verification and Optimization
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:
Code:
adb shell setprop dalvik.vm.execution-mode int:portable
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.)
Priorties [credits zeppelinrox]:
Code:
BACKUP_APP_ADJ:I = 0x7
FOREGROUND_APP_ADJ:I = 0x0
HEAVY_WEIGHT_APP_ADJ:I = 0x4
HOME_APP_ADJ:I = 0x0
PREVIOUS_APP_ADJ:I = 0x5
SERVICE_ADJ:I = 0x6
SERVICE_B_ADJ:I = 0x8
VISIBLE_APP_ADJ:I = 0x3
Source: elinux
Thanks mate I was looking for this. Going to test it .
Sent from my GT-I9000
Isn't superchargers buletproof launcher same thing?
sent from the SGS TITAN and stuff
Works !
MfG
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?
jjlwork said:
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?
Click to expand...
Click to collapse
Just pm me the services.jar file from framework folder and the build.prop file... will make a package and add here for everyone.
mnazim said:
Just pm me the services.jar file from framework folder and the build.prop file... will make a package and add here for everyone.
Click to expand...
Click to collapse
sent Thank You!
Wow, thanks for the quick update! Will test tonight
EDIT: Flashed it, and have been running with it for a few hours now. Played around with lots of apps in the background including some memory-hogs etc.
Disclaimer: Devices react differently to different things, results may vary.
Verdict: Looking good! Seems smoother overall, and no redraws yet! Definitely recommended by me
Have always been a fan of the supercharger script so I'm pleased to see an i9000 specific solution appear.
However in Slim Bean 2.1, the default launcher has an option to lock it into memory. Works pretty well, but there is an occasional redraw.
Will this script remove redraws completely? If not, then there's little point in using it with the slim bean ROM at the moment.
Sent from my GT-I9000 using Tapatalk 2
All Day On XDA said:
Have always been a fan of the supercharger script so I'm pleased to see an i9000 specific solution appear.
However in Slim Bean 2.1, the default launcher has an option to lock it into memory. Works pretty well, but there is an occasional redraw.
Will this script remove redraws completely? If not, then there's little point in using it with the slim bean ROM at the moment.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Flash this and avoid ticking that option. If that option is ticked the launcher will be redrawn on heavy RAM reqs. With this no matter what the launcher will not be killed.!
sorry for the question, but can i use this mod only with stock Kernel?
MfG
warhead1978 said:
sorry for the question, but can i use this mod only with stock Kernel?
MfG
Click to expand...
Click to collapse
It has nothing to do with kernel.
I decided to install this and honestly I haven't noticed much difference from stock.
I wonder if it is because I use the Homehelper component of Widget locker.
I think your script is not picking up the true home launcher because of this.
Sent from my GT-I9000 using Tapatalk 2
my phone feels a lot slower when I flash this. yes, the launcher doesn't close, but it seems like it's sitting in my RAM and using up my CPU (maybe) while i'm using other apps. am i imagining things? i don't know how this fix actually works
Not a single redraw since I installed this. Guys if you have lag problems increase vm heapsize.
Thanks for this.
fatino said:
Not a single redraw since I installed this. Guys if you have lag problems increase vm heapsize.
Click to expand...
Click to collapse
What's vm heapsize? or where do I change that?
jonafun said:
What's vm heapsize? or where do I change that?
Click to expand...
Click to collapse
You can use Ram Manager to easly change heapsize. Try 128MB.
AFAIK it is amount of memory that each app can use. If its too low apps become slow or system kills them. Correct me if Im wrong.
Flashed this mod last night. Works brilliantly
I9000 CM10 nightly
What about building JB or ICS from source for DesireZ?
I remember virtuous quattro was an ICS rom build from vanilla AOSP. It was faster and cleaner than CM9 based rom.
I think a pure aosp build of JB or ICS with new drivers it would speed up a lot these new android version on our devices.
I'm ready leave all CM feature for a pure google AOSP with some speed.
I think you'll probably still need all the tweaks that the andromedus team has done to make it a dd
Sent from my HTC Vision using xda app-developers app
nagash91 said:
What about building JB or ICS from source for DesireZ?
I remember virtuous quattro was an ICS rom build from vanilla AOSP. It was faster and cleaner than CM9 based rom.
I think a pure aosp build of JB or ICS with new drivers it would speed up a lot these new android version on our devices.
I'm ready leave all CM feature for a pure google AOSP with some speed.
Click to expand...
Click to collapse
I use http://forum.xda-developers.com/showthread.php?t=1605016 and I'm very happy with it - 4.1.2 but also has goodies that you need anyway. Clean source ROM would nice though - just to try it out I agree - but I personally would miss a lot of stuff.
Device: Samsung Galaxy S3 SGH-I747
Network: AT&T
ROM: [ROM][4.2.2][OFFICIAL] LiquidSmooth v2.2 - d2att - 4|12|13
Kernel: 3.4.39-leanKernel-att_aosp_43-5.3.4-+ [email protected] #20 Wed Apr 10 22:31:57 PDT 2013
I am still kinda new this this ROM and was just wondering what kernels out there would work with my device or wich ones do you guys like using so that i can read up on those and see wich would be the best fit for me
Checkout ktoonsez kt-747 kernel
Any of the aosp JB ones should work. Task's, the underwear one and lean kernel should for instance. Most of the ROMs are based off of CM source and each of the kernels I mentioned are also based on CM code. Hence, they all play together nicely (for the most part).
Sent from my SAMSUNG-SGH-I747 using xda premium
Is there a ROM that has a Pure or ALMOST Pure AOSP 4.4 KitKa For Maguro Galaxy Nexus?
Many of the current roms use CM11 base or are derivative of CM11 code.
4.4 CM11:
- cMetal
- Dreams
- Experience Project
- KitKang
- PlayfulGod's CM11 Unofficial
(they all likely use the same base, only differences are the cherry picks they merged into the rom)
PA had a pure AOSP 4.4 build but it's unsupported. Haven't checked out Gummy or SlimKat's sources - might want to look into those.
ROM development will definitely pick up after the kernel is brought up to the necessary changes to fix webview lag, that is the largest 'unfriendly' bug so far with getting maguro to 4.4.