So no news on the link being down??

Originally Posted by hima1978

Dear,
I am a newbie here so please bear with me
I managed the service jar, but how do i know what percentage do you show supercharged when you run the script?
I go to SManager and run the script, then i choose the speed 0-3 ( i choose 0), then i get the options 1-17 (i tried different ones, last one was multitasking, and i get the attached screen!
Can you help me with that am i doing wrong, and how to fix it

Recommendation 1: Wait for Zep or wraithdu because they know more about ICS than I do

Recommendation 2: I would run the sqlite binary installer found HERE then try supercharging with the latest V6 script in the same post.


Also, trying different settings is a good thing but be sure to try settings appropriate for your phone. The info I found on the SGS2 says it has 1GB of memory so either the 768HP, 1000HP or my personal favorite No. 10 custom setting will probably work best for you.

After getting supercharged error free you will reboot (superclean recommended) and run the script again. What you are ultimately looking for is 100% supercharged and you'll see it when the script stops scrolling.

I ran the new test2 script and installed the starter kit before. Everything seems to be ok, 100% charged, but after starting the script again, it gave me NO to some functions which should run on boot (see screenshots). Why?

There were no hints to start another script except 99SuperCharger.sh or did I miss something?

Originally Posted by Daniel D.

I ran the new test2 script and installed the starter kit before. Everything seems to be ok, 100% charged, but after starting the script again, it gave me NO to some functions which should run on boot (see screenshots). Why?

There were no hints to start another script except 99SuperCharger.sh or did I miss something?

When you went through the Driver Options (29) did you answer "yes" to the ones you want to run on boot?

I looked into the settings, but I can only set scrolling speed (2) and animations (off of course). Hmmm, strange.

Wow.... this script is like... addicting, eh? bizy bizy... lol

Originally Posted by prboy1969

Thanks for this Zepp . So are we headed toward a no Script Manager needed to run V6 SuperCharger ?

When it's an app... you can always use terminal

Originally Posted by Rydah805

Wait, even with your sqlite and zipallign installer, it says It's not installed.

Check if they are or aren't in /system/xbin

Originally Posted by lessthanzach

Is this an issue or no worries? I extracted the folder to the root of my internal sd card before running the script.

Ah... you found a bug... I'll fix it. I guess your toolbox doesn't have a chmod for some reason...
Anyway I forgot to assign chmod to the busybox that it's installing.

Originally Posted by PieceKeepr

What changed between V6 RC9 test 1 and test 2?

About another 100 lines
Tweaked messages and code.
Rearranged /init.d/*99SuperCharger a bit
Added checks to see if sqlite3 and zipalign binaries exists
SuperClean will wipe cache partition again along with dalvik

Originally Posted by 1stichiban

Thank you very much for your hard work.
will try this out and let you know how it works out.

Edit: Ran startmeup.sh. Then ran test2. I selected fix emissions and zipalign to run on boot via driver options. Was able to get 100% supercharged.
Checked the log file for supercharger it showed applied via system/.....
But when I checked log file for zipalign and fixed emissions there was no entry that it ran on the recent boot.
Does it mean that these did not run on boot? Or does the entry in the log file of supercharger include all the features selected to run on boot in driver options?

If they run on boot, all scripts will have the /data/Ran* file.
If it exists, it ran.

Originally Posted by Black_jackss

No,when I cooked my rom I still incule init.d intact

Since when do you cook?

Originally Posted by Adrian DC

Thanks, it works fine.
However, I'd recommend you to add a rw remount of the data folder aswell,
because for some like me, the data isn't rw by default on stock ROMs.

busybox mount -o remount,rw /data 2>/dev/null
busybox mount -o remount,rw /system 2>/dev/null

Doing that, the scripts works perfectly.
Bye!
ADC

Weird... guess it wouldn't hurt to throw it in for ****z n giggles.

Originally Posted by hima1978

Dear,
I am a newbie here so please bear with me
I managed the service jar, but how do i know what percentage do you show supercharged when you run the script?
I go to SManager and run the script, then i choose the speed 0-3 ( i choose 0), then i get the options 1-17 (i tried different ones, last one was multitasking, and i get the attached screen!
Can you help me with that am i doing wrong, and how to fix it

Use latest version and you won't get those errors.

Originally Posted by markapowell

Alright, I ran unsupercharger, and removed the v6 file. Rebooted, ran script fine. Went through drivers options, integrated, right (?) and calculated, then rebooted and then came up that values don't match.

Do you have /data/Ran_SuperCharger.log?
If it exists, it ran.

Originally Posted by metalspring

Well I tried your newest test release with zipalign and the new interface for the DB optimization and it wouldn't detect the sqlite file (I used part of your other script to install since I don't need or want the su binary or the busybox installer, both of mine always work perfect) and then I tried the wheel alignment and immediately got force closes everywhere and a hot reboot. Even after pulling the battery and then wiping dalvik I got stuck on the bootanimation

Now for good news, it seems as if from devs are actually paying attention to v6 now because pretty much any newer rom I flashed on the gnex has already had the services jar patched with your values- icsourcery, liquid, and newer builds of aokp

Don't sound like it worked perfectly.
At least use the fixed su binary.
I've seen segmentation faults in log files after reboot.
I had forgotten to update the su binary after flashing a rom update.

Yep.. it's quite popular on GNex now

Originally Posted by HamishAlexander

If it's a rip off, does it work the same way? RM have better interface, you gotta admit that.

Thanks, i'll do it after my eyes stop bleeding from OP-post.

Besides that original design style of yours i got no complaints, thank you for your work, men like yourself are truly pillars of Android community and i'm proud to talk with you here.

Like they say... "You can put lipstick on a pig - but it's still a pig"

No, it doesn't come close to what SuperCharger does.
It echoes adj values (1 small thing that SuperCharger does) and claims that it's a unkillable launcher.
It's a lie. It does nothing for the launcher.
It may as well claim to wipe your ass for you because both claims are equally true.

And yes, it pisses me off that somebody took a small part of SuperCharger and uses it to rip people off.

They also say "There's a sucker born every minute."

Originally Posted by oikhlail11

umm why is the patching framework site down? i want to patch my system.jar but the site is down

It's up now... some maintenance was being done.

Originally Posted by dejanxxxx

Complain me this for die hard battery calibrate.Pise leave it for 20 minutes extra calibrate.da then you should be in smanager 20 min and then run the calibration, or what I should do first, complain to me-20min left.What should I do?

Just use Automatic mode.

Originally Posted by paranoid2007

No criticism intended. I just wanted to make a suggestion based on my observations. BTW, I'm 100% supercharged and I really don't know, why the launcher still gets killed sometimes. A 100% sure way to get the launcher killed is to update an app through Google Play. This always leads to a restart of the launcher afterwards. ICS seems to have some strange behavior. Nothing of that sort happened under Gingerbread.

Yeah... I'm looking at further smail edits

Originally Posted by PieceKeepr

When you went through the Driver Options (29) did you answer "yes" to the ones you want to run on boot?

If it's not a yes... it's a no

Originally Posted by Daniel D.

I looked into the settings, but I can only set scrolling speed (2) and animations (off of course). Hmmm, strange.

You don't have an init.d folder.
Either you're on a stock rom or your rom doesn't have init.d support

Originally Posted by zeppelinrox

Ah... you found a bug... I'll fix it. I guess your toolbox doesn't have a chmod for some reason...
Anyway I forgot to assign chmod to the busybox that it's installing.

Hmm, that's gonna be a problem... you can't chmod busybox to be executable without chmod. Maybe it's just the chmod symlink to toolbox that is missing, and you can call 'toolbox chmod ....' / 'toolbox chown ....'

Yes but it's all about the sequence of events... I re-arranged a bit and ended up making a bug

This already gets applied early in the script using whichever chmod the device is using:

chown 0.0 /data/local/busybox.v1.19.4/xbin/busybox; chmod 04755 /data/local/busybox.v1.19.4/xbin/busybox

The problem is that all busybox binaries are removed and then simply call chmod and chown without specifying that /data/local/busybox.v1.19.4/xbin/busybox should be used

Just gotta use your trick and add

CHOWN="$BB chown"; CHMOD="$BB chmod"

And in the last part, use $CHOWN and $CHMOD instead of "chown" and "chmod"

Originally Posted by zeppelinrox

Don't sound like it worked perfectly.
At least use the fixed su binary.
I've seen segmentation faults in log files after reboot.
I had forgotten to update the su binary after flashing a rom update.

There was another thing I was curious about...the sqlite file- do we really have to install the one you provide? I know the one I have is supposed to have support for the sqlite optimization (worked on all the previous versions) and its larger so I'd have to assume it has even more functionality
Its no big deal since many gnex roms have built in options for zipalign on boot and I have an app that does sqlite optimization on boot, I usually use the roms built in fix permissions as well (just to avoid potential issues using a third party script)

Nah I made it up for those that don't have it.
Not sure why sqlite is sometimes so much bigger even if it's the same version as the small one.
I haven't noticed any difference in functionality... I don't think there can be.

wraithdu has experienced this while compiling the su binary, if memory serves.
The first time he did it, it was huge.
The second time, it was the usual size.

Does the sqlite app do all possible dbs?

Your zipalign script probably misses the vendor/apps - I haven't seen one that does it yet but I added it, of course

As for the fix permissions... the one I came up with, I'm sure, can't be beat.
It's been tested alot in this thread and I managed to fix a common issue with missing contact pictures One user would have them go missing with every fix permissions script that he tried but it works now. hehe

It's fast too... about 300 app permissions per minute give or take a few.
The fix permissions script in my recovery can take about 10 minutes for the same number of apps.