• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root V6 SuperCharger

Scur

Android Expert


Hope everyone checking this out has luck.. I would but don't have time currently reflash if something goes wrong.. One thing I did notice is that it said that BusyBox 1.18.2 or lower was a requirement and you would receive errors on anything higher.. Not sure what 0728 comes with normally or if TITU installs it but it is showing BusyBox 1.18.4.. Downgrade may be necessary to make it probably work.. Just a thought, don't honestly know as i haven't tried.. Throwing it out there ;)


With 0728, the Busybox installer shows I have 1.16.2 already installed, so it's low enough.

I just installed it, and my phone is running. I haven't put in the updates yet, but I'm about to. Then I'll touch base in a day or two about any differences I might notice.

edit: I installed both updates, rebooted, waited for the phone to settle down, cleared the cache to make sure, and ran Antutu. The first time I ran it (or got it to run without crashing, I should say) my stats were pretty much the same, except my 2d graphics was 173, in line with the rest of you, instead of 110 to 140 like it's been all along. I was all Right On! and ran it again. This time, my 2d was at 25, and the rest sucked, too. Even with a class 10 card, my total was 599. What that means, I haven't the foggiest.

In the end, I'm not sure if it's snappier yet or not, but it definitely doesn't feel slower.


I played with this last night. I went with "9" which is the "gaming setting" (I forgot to run AnTuTu before I did it to see what my score was) but my total score after doing it and running AnTuTu is 791. Of course what does that exactly mean? I have no clue.

I cant exactly say I have noticed a difference.


Edit- I did run AnTuTu a couple days ago and when I went to "Score Chart" I was at the bottom of the list below the Wildfire which now I'm actually beating the WildFire.


I've only started playing with this, and found that I can greatly affect my performance, so I thought it should have it's own thread, instead of us talking about it in the CM7 thread.

I'm using the free Fruit Ninja app to gauge graphic lagginess. Before I installed the v6 script, I could barely play FN. When I tried preset 2, it kept locking up, trying to force close, and I couldn't do anything. My latest settings of 12, 24, 100, 125, 175, 200 actually made it playable, still a little laggy, but definitely an improvement over the original settings. My app drawer scrolls up and down with no lag now too, where it used to have a bit of lag. I think it's time for me to do some more research about V6 and find out EXACTLY what I'm changing, and what my limits are. Most of the stuff I see so far is about improving the performance of a phone with 512 mem. What that means for us, I have no idea yet. :/
BTW, I have my sd-ext set at 1024 with a 128 swap, and sdboost set at 2048.

I have a whole new way of tinkering with my Ascend now. :)
 
So after trying several of the default settings, I'm having the best performance with option 6, balanced settings 3.
I'm having trouble, though, keeping the settings after a reboot. It keeps resetting to much higher settings. Also, I can't read the SuperCharger.html in my sdcard root for the help menu. It's an empty file.
 
Hope everyone checking this out has luck.. I would but don't have time currently reflash if something goes wrong.. One thing I did notice is that it said that BusyBox 1.18.2 or lower was a requirement and you would receive errors on anything higher.. Not sure what 0728 comes with normally or if TITU installs it but it is showing BusyBox 1.18.4.. Downgrade may be necessary to make it probably work.. Just a thought, don't honestly know as i haven't tried.. Throwing it out there ;)

I just read that TB has its own internal version of BusyBox it uses itself, for some reason. To see the BusyBox used outside of TB, run the BusyBox Installer. You can pick any version you like. I bumped up to 1.18.2 and everything seems fine.
 
what does this do?

Let me quote zeppelinrox here...

Android puts each running app into 1 of 6 Out Of Memory (OOM) groups based on their priority.
FOREGROUND_APP, VISIBLE_APP, SECONDARY_SERVER, HIDDEN_APP, CONTENT_PROVIDER, and EMPTY_APP.
The default minfree values ("kill thresholds") for each OOM group are, as far as I can tell: 6, 8, 16, 20, 22 and 24 mb. (CyanogenMod 6.1.2)
This means that: when free memory lowers to 24 mb, EMPTY_APPS get killed; at 22 mb free ram, CONTENT_PROVIDER apps get killed; and so on...


V6 let's you define those minfree values, affecting how many processes the phone runs at any given point. When I massively lower the last three slots in my phone, and raise the third slot, my phone runs far faster.
This is what Auto Memory Manager does. It adjusts these values (you can also see which apps are running in which slots with AMM) and saves them to a script. V6 will also do this, but adds a couple options, and assigns certain processes to certain slots. If zeppelinrox is to believed, it's a more complete solution.
 
How AMM defines the slots...

1. Foreground Application - An app that you currently see on the screen. This also includes System and Phone.

2. Visible Application - An app that is visible to the user but not at the front, possibly because of transparency, etc.

3. Secondary Server - These are applications and services running in the background. It includes SenseUI or Launcher(Home) so don't set this too high.

4. Hidden Application - Apps that are not visible but are still running in the background.

5. Content Provider - Processes that provide for others e.g. Contacts content provider, Calendar content provider, etc.

6. Empty Application - Apps that are essentially in standby and are not doing any work. They can be shut down.
 
The only thing is, I can't get it to save my settings. So until I've spent some time to see if it will save the app memory locations so I can just use AMM for the OOM settings, I'm having to run it all over again after a reboot. It only takes a minute, so it's not a huge deal, but still annoying.
 
Same here, cannot keep settings after reboot :(

Yeah, I tried readjusting permissions to the settings file it creates like I read some others did, and still couldn't get it to stick. So, I just made my launcher HardToKill, since that sticks, then used Auto Memory Manager for the values.

edit: After a bit more research, I see that you run the script, make your launcher HTK (if you do make your launcher hard to kill, make sure that Menu > CyanogenMod Settings > Performance > Lock home in memory is unchecked), change your OOM settings, then exit. Then you have to run the 99SuperCharger file as root and on boot. Do this in Root Explorer by navigating to system/etc/init.d, hitting the Mount R/W at the top to mount as read/write (it's only temporary), long pressing on 99SuperCharger, hitting permissions, then checking Owner=read,write,execute, Group=read,execute, Others=read,execute. Trying that out myself after breakfast. The pancakes are not a lie.

edit 2: Yeah, that worked for me. Cool. So I'm uninstalling Auto Memory Manager now. One less app in my drawer.
 
So I went to run this again since Ive had to reflash since I ran it the first time. And found theres a new update out for it with different settings. Its update 8. (Ill attach the script at the bottom) I ran AnTuTu before hand and my overall was around 637 without running the script. I ran the script went with option 9 again, which before was "Gaming settings" but now with the update8 V6 its "Mega RAM 2 + Hard to kill Launcher" Heres 3 runs on AnTuTu I did after running the script. I always run atleast 3 times just to get an average because I never get the same readings twice.

But first heres what I have my phone set up on:
CM 7.2 07282011 oc'd @710
Sd card- cheap 10 dollar WalMart special SanDisk Class 4 4gb partitioned at 512mb EXT 32mb Swap, Delvik on SD
BusyBox- 1.18.2

(Your SD card read and write play a part on your over all score in AnTuTu. If you have a better card the higher your SD readings will be which will add to your overall. Like I said I have a cheap 10 dollar WalMart special SanDisk Class 4 4GB)

Option 9 "Mega RAM 2 + Hard to kill Launcher"

Run 1:

RAM:114
CPU Integer: 236
CPU Float Point: 20
2D graphics: 170
3D Graphics: 88
Data Base OI: 50
SD Card Write: 39
SD Card Read: 78
Total Score: 795

Run 2:

RAM:111
CPU Integer::236
CPU Float Point:19
2D Graphics:174
3D Graphics: 85
Data Base OI:55
SD Card Write: 44
SD Card Read: 84
Total Score:808

Run 3:

RAM:117
CPU Integer:246
CPU Float Point:19
2D Graphics:172
3D Graphics:84
Data Base OI:50
SD Card Write: 42
SD Card Read: 75
Total Score: 805




Ran AnTuTu again after posting this and got my highest score ever so I had to share.

RAM:115
CPU Integer:243
CPU Float Point:20
2D Graphics:173
3D Graphics:87
Data Base OI:60
SD Card Write: 42
SD Card Read: 74
Total Score: 814!!!
 

Attachments

It doesn't work for me, crap!


You might try to run the 99 script wth the as root and on boot both checked, after adjusting the permissions. It won't run, you'll get an error, so just back out. See if that gets it going for you.
 
Errrr I cant get this to stick for the life of me. I wonder what would happen if I ran it at boot? Might try it.

Also I found this script too: Ram Optimizer/Rom speed booster by Juwell. Havent noticed to much of a difference yet. But this one is flashable thru Clockwork recovery.
 

Attachments

Errrr I cant get this to stick for the life of me. I wonder what would happen if I ran it at boot? Might try it.

Also I found this script too: Ram Optimizer/Rom speed booster by Juwell. Havent noticed to much of a difference yet. But this one is flashable thru Clockwork recovery.

I THINK I got mine to stick by running the SuperCharger script, getting everything the way I wanted, ducking out, changing permissions on the 99SuperCharger file, then trying to run the 99 file with the script manager, checking As Root and On Boot. The script wont run of course, but it may set the On Boot part, I just exit back out after I get the error message. This MAY have been the way I got it to run on boot. I'll play around a bit later to test out that little theory.

DON'T RUN THE SUPERCHARGER SCRIPT "AT BOOT"! It's only a script that creates and edits the script that changes the OOM settings.
 
Ive tried running the 99Script too. I found this video on youtube, he''s doing it with a Droid X tho, he runs V6 picks his settings hits 17 gets exit code 0 which I get too, but then he goes to the 99Script runs as root and boot and gets the exit code 0 again, then reboots his phone. When I run the 99Script I get the code of 1, How is he getting exit code 0? Everytime I get the code of 1. Maybe thats the problem? I dont even know how to go about getting the exit code of 0 in 99Script tho and to be honest dont even know what exit code 0 or exit code 1 means.V6 Supercharger HTK & Bulletproof Launchers all android devices Tutorial - YouTube
 
Ive tried running the 99Script too. I found this video on youtube, he''s doing it with a Droid X tho, he runs V6 picks his settings hits 17 gets exit code 0 which I get too, but then he goes to the 99Script runs as root and boot and gets the exit code 0 again, then reboots his phone. When I run the 99Script I get the code of 1, How is he getting exit code 0? Everytime I get the code of 1. Maybe thats the problem? I dont even know how to go about getting the exit code of 0 in 99Script tho and to be honest dont even know what exit code 0 or exit code 1 means.V6 Supercharger HTK & Bulletproof Launchers all android devices Tutorial - YouTube


Alright I figured it out how to match this guys video and get the script to stick and get the exit code 0 when you run the 99Script. Heres the trick. I opened root explorer and mounted as R/W and then ran the V6 Script and then 99 Script marking Run at Root and Run at Boot for the 99 and you will get exit code 0 then reboot your phone. And its sticks!
 
Alright I figured it out how to match this guys video and get the script to stick and get the exit code 0 when you run the 99Script. Heres the trick. I opened root explorer and mounted as R/W and then ran the V6 Script and then 99 Script marking Run at Root and Run at Boot for the 99 and you will get exit code 0 then reboot your phone. And its sticks!

Nice catch. I forgot I was changing to read/write. Makes perfect sense.
 
Alright I figured it out how to match this guys video and get the script to stick and get the exit code 0 when you run the 99Script. Heres the trick. I opened root explorer and mounted as R/W and then ran the V6 Script and then 99 Script marking Run at Root and Run at Boot for the 99 and you will get exit code 0 then reboot your phone. And its sticks!

Wait. Once you mount as r/w, doesn't it unmount when you exit Root Explorer?
 
if your using DTa2sd than this wouldnt be needed with a class 4 or higher, but also if your trying to use this v6 and a2sd, than that might be your problems right there.
 
Wait. Once you mount as r/w, doesn't it unmount when you exit Root Explorer?

Thats what I would think but if you mount as r/w and hit the end key it stays as r/w until your phone reboots then it'll switch back to r/o


if your using DTa2sd than this wouldnt be needed with a class 4 or higher, but also if your trying to use this v6 and a2sd, than that might be your problems right there.

Errrr you maybe right. Ahaha But my home screens and such do seem a snappier. I have the transition of home screens set to "scatter" and it "scatters" so fast it looks like its just set on the normal slide to the next page that its set on by default
 
Thats what I would think but if you mount as r/w and hit the end key it stays as r/w until your phone reboots then it'll switch back to r/o




Errrr you maybe right. Ahaha But my home screens and such do seem a snappier. I have the transition of home screens set to "scatter" and it "scatters" so fast it looks like its just set on the normal slide to the next page that its set on by default

You're right, it stayed on r/w, but ONLY when I made it r/w all the way down. That is, when I started Root Explorer, I mounted as r/w, then went into system, made that r/w, then the rest were all r/w already. When I just tried to make the init.d folder w/r, it didn't hold. Again, nice catch on the trickiest hurdle. It's all cake now.

And I KNOW my launcher is quicker with it as hard to kill. I've been putting widgets back on my Launcher Pro, and it still runs nice.

As far as my system goes, I've been steadily adding apps that seemed like they would bog my system down. I was using option 6, and was seeing my phone get laggy. I just switched to 8, and it perked right up. I don't know if you noticed, but CM7 puts the OOM limits in the neighborhood of option 8, with some differences in the middle slots. I'm gonna keep playing around now that I don't have to luck into getting them to save. :)
 
Yeah but I saved a nandroid when I had it running fast and super smooth so I just keep restoring that so it goes back to the same exact way it was running before and incase I changed other settings else where I dont have to remember those too.
 
Back
Top Bottom