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

Root V6 Supercharger and the Evo LTE

I tried option 5, and thought I made progress when I was up to 13 web pages, but when I tried for 14, it killed my browser.

I switched back to the Nova launcher before that.

Trying 6 now. Many thanks for the link. :)

Edit -

Feel like I'm chasing my tail.

Supercharger removed (option 15), trying viper's Ultimate 2.1 (and back to stock zip already d/l :D ;)).
 
With viper, it's fluid and quick, plenty good on the battery, but it's not terribly multitasky.

edit - I have something idiosyncratic in my post-boot script, gave feedback to viperboy, ignore above comment until that's ironed out.
 
EarlyMon said:
Here's my latest startup -

7181671413_c733285075_z_d.jpg
Click to expand...
Hey EM, how do you get Quick System Info to display the cpu and memory values? Mine only shows the graphs even with all options checked in preferences? (sorry it's off topic)

7380299610_650aac8d92_m.jpg
 
Ok, now isn't this interesting.

I was having trouble with viperboy's dual core mods, he suggest that I see if there were anything in /system/etc/init.d causing conflicts - and I found V6 in an init script there.

So - I went back to my day 1 stock rom. No /system/etc/init.d existed.

Then I went back and re-installed Charmeleon (not nandroid restore, re-install).

The init.d subdir reappeared and this is in one of the scripts -

Code: 
# V6 SuperCharger, OOM Grouping & Priority Fixes created by zeppelinrox.
echo "25,35,75,90,150,250" > /sys/module/lowmemorykiller/parameters/adj;
echo "1536,3072,19200,25600,32000,38400" > /sys/module/lowmemorykiller/parameters/minfree;
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "500" > /proc/sys/vm/dirty_expire_centisecs;
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs;
busybox sysctl -w kernel.panic_on_oops=1;
busybox sysctl -w kernel.panic=0;

#Kernel
echo "NO_GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features;
echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features;
echo "NO_NORMALIZED_SLEEPER" > /sys/kernel/debug/sched_features;

Charmeleon is already V6'd based on what the Charmeleon dev thought made sense.

Hmmmmmmmm........
 
EarlyMon said:
Ok, now isn't this interesting.

I was having trouble with viperboy's dual core mods, he suggest that I see if there were anything in /system/etc/init.d causing conflicts - and I found V6 in an init script there.

So - I went back to my day 1 stock rom. No /system/etc/init.d existed.

Then I went back and re-installed Charmeleon (not nandroid restore, re-install).

The init.d subdir reappeared and this is in one of the scripts -

Code: 
# V6 SuperCharger, OOM Grouping & Priority Fixes created by zeppelinrox.
echo "25,35,75,90,150,250" > /sys/module/lowmemorykiller/parameters/adj;
echo "1536,3072,19200,25600,32000,38400" > /sys/module/lowmemorykiller/parameters/minfree;
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "500" > /proc/sys/vm/dirty_expire_centisecs;
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs;
busybox sysctl -w kernel.panic_on_oops=1;
busybox sysctl -w kernel.panic=0;
 
#Kernel
echo "NO_GENTLE_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features;
echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features;
echo "NO_NORMALIZED_SLEEPER" > /sys/kernel/debug/sched_features;

Charmeleon is already V6'd based on what the Charmeleon dev thought made sense.

Hmmmmmmmm........
Click to expand...


Wow, well if what you're saying stands correct, and he has in fact baked this tweak into the ROM, then he needs to update his OP on XDA to clearly reflect this tweak. One, it's blatantly listed as V6 Supercharger and there's no credit provided to the V6 dev that I can see. Two, so that others can avoid reinstalling the script over the top of this and tweaking it, potentially degrading the performance of the ROM.

Since you've already been in contact w/ Viper, EM, you might want to call this out via PM. That's a pretty big oversight on his part.

**EDIT** - NVM, it's Joelz ROM in which this is baked into, correct? I'll PM him. I haven't tried Viper's ROM yet so I am unsure if he too has baked the script or taken pieces of it w/o credit.
 
Yep, it's baked into JoelZ rom - I've been in touch with him about the init scripts defect and what I think the right values might be for adj and minfree (see my post here in our Charmeleon thread) and confirmed that came from his rom, but I spaced double-checking credit.

JoelZ seems pretty darn good about credits, thanks for PM'ing him.

I checked viperboy's init scripts, found no evidence of V6 use.
 
EarlyMon said:
Yep, it's baked into JoelZ rom - I've been in touch with him about the init scripts defect and what I think the right values might be for adj and minfree (see my post here in our Charmeleon thread) and confirmed that came from his rom, but I spaced double-checking credit.

JoelZ seems pretty darn good about credits, thanks for PM'ing him.

I checked viperboy's init scripts, found no evidence of V6 use.
Click to expand...


Yep, and he's been around long enough to where I'm sure it was just an oversight. It happens. Thanks for checking out Viper's!
 
This script wasn't nearly this complicated on the OG. I just set up script manager and ran the darn thing for my memory capacity, it worked right out the box. LOL

I'll have to play with this when I get some free time. :)
 
Selecting V6 optimizations for this phone gets the EMPTY_APP parameter set high - that param says, if memory falls below this point, start clearing out your cached apps.

That's exactly the multitasking problem this phone has in the first place, hence both IOWA and I finding a different blend of params, and that one in particular lowered, to work out better.

IOWA's settings do a bit better on multitasking, but at the expense of some response in my trials, so I tweaked settings just a bit differently.

Your mileage may vary on V6, but I don't think it fits the special case of our particular phone setup.
 
Ok.

The earlier V6 SuperCharger that I used is basically for Gingerbread and not right.

The one to use is -

V6_SuperCharger_for_Android-Update9_RC9_Test_18.sh

It produces optimizations on the first pass that includes aligning initialization scripts, setting memory values not found in the options list, and automatically updating the services.jar file.

Suggest that you let it perform all the tweaks that it wants to.

When done, edit /system/etc/init.qcom.post-boot.sh in the msm8960 case and remove any updates to adj or minfree files (the V6 doesn't know about those).

The V6 optimizations reduced my synthetic benchmark results slightly, but so far it feels ok, and it might be the multitasking answer.

More testing to follow.

PS - I completely verified that this overrides, and doesn't collide with, the V6 SuperCharger settings baked in to the Charmeleon 5.0.0 rom.
 
Feel free to kang this post like a red-headed step-child, you have my official permission. :)

xda-developers - View Single Post - [ROM] 06.03 - HUGE Changelog - Charmeleon Rom v5.0.0 - EQS with tabs | Tweaks

EarlyMon said:
Be sure to use this version -
V6_SuperCharger_for_Android-Update9_RC9_Test_18.sh

And let it auto run everything for ICS. The 9-8.2 revision isn't ICS savvy.

Then go into /system/etc/init.qcom.post_boot.sh find the msm8960 case and remove the echo to adj by commenting out that line with the # character.

Otherwise, your out of memory adjustment won't come from V6, it'll come from that line and you don't want that.

For those PM'ing me and confused about my memory statements, here's an easy-to-use pre-edited post boot file.

To use -


  • Make a nandroid backup!!
  • Download the attached zip
  • Put it on your sd card
  • Unzip with EStrongs File Explorer
  • In EStrongs, long press, then unzip
  • In Strongs, menu, settings, check on Up to Root, Root Explorer, and Mount File System
  • In EStrongs, long press on the sh file, Open As, Text, ES Note Editor -- if you need to edit it
  • In EStrongs, long press the sh file and Copy to /etc, overwrite existing file
  • In EStrongs, in /etc, long press this post boot sh file, Properties, make sure permissions are rw-rw-rw-
  • In EStrongs, menu, settings, check off Mount File System
  • Reboot



How to use:

The block you care about is bracketed by comments marked "##EM# begin" and "##EM# end"

If you are using the ICS-compliant V6 SuperCharger or freeza's kernel tweaks, do not edit the file.

If you are using stock Charmeleon with no other tweaks, uncomment the two lines indicated to overcome the bug in this file (JoelZ knows about it).

If you want to try my earlier minfree settings (even though I now am going with V6 myself), follow the instructions to leave the first minfree commented, and uncomment the second minfree line.

Comments are marked with a # character.

If either one of us screwed something up in this process, restore your nandroid. Can't help you if you don't make a nandroid backup first.

Hope this helps. :)






If you want to try the V6 SuperCharger:

Get the right V6 from here - xda-developers - View Single Post - [Script][U9RC9T18] OOMptimize with the -=V6 SuperCharger=- and Kick Lag's Ass!!

Save the pdf without the .pdf extension - it's really just an sh file in disguise.

Follow the instructions for it here - xda-developers - View Single Post - [Script][U9RC9T18] OOMptimize with the -=V6 SuperCharger=- and Kick Lag's Ass!!
Click to expand...

View attachment init.qcom.post_boot.sh.zip
 
I am getting so frustrated with this script...I have no idea what I'm doing wrong, but I can't get the oom/supercharger to stick. I've installed the starter kit, run the new services.jar, set script manager to run 99supercharger at boot...nothing is working. I even commented out the adj line early suggested, even though I'm running a different rom. this script is questioning my manhood
 
jackgibbs said:
I am getting so frustrated with this script...I have no idea what I'm doing wrong, but I can't get the oom/supercharger to stick. I've installed the starter kit, run the new services.jar, set script manager to run 99supercharger at boot...nothing is working. I even commented out the adj line early suggested, even though I'm running a different rom. this script is questioning my manhood
Click to expand...

If you're running freeza's work or work that copies his, then you have an init.d bootup process that detaches sub-processes and constantly makes their own adjustments while you're running.

In freeza's case, if you want the V6 to stick, you have to install his stuff, install V6, then boot once, then manually strip out the offending functions in his init.d script, then reboot - and that's assuming he hasn't added anything even craftier since I last looked.

V6 and normal stuff sets the whole thing up at boot time.

The performance roms not only set up at boot time, they're constantly tweaking those parameters the whole while you're running.

That's why V6 seems to be doing nothing - it's being overridden shortly after boot, or just as soon as you turn screen off then on, to trigger their mods.

That's the deal.
 
hmm. I'm using flex's ultrasmooth stock, which uses viper's base. He doesn't say anything about freeza in the op, so I doubt that stuff is in there. I also don't have a system/etc/init.d folder, but I have an init.rc...could that hold the same type of info?

also, the ran_supercharger.log isn't even showing it running at boot at all, and I have it set up the same way I have the 97bulletproof_apps script set up in script manager, and that one is running fine.
 
jackgibbs said:
hmm. I'm using flex's ultrasmooth stock, which uses viper's base. He doesn't say anything about freeza in the op, so I doubt that stuff is in there. I also don't have a system/etc/init.d folder, but I have an init.rc...could that hold the same type of info?

also, the ran_supercharger.log isn't even showing it running at boot at all, and I have it set up the same way I have the 97bulletproof_apps script set up in script manager, and that one is running fine.
Click to expand...

I used freeza as an example of an OG front-runner that I know and trust and whose work I understand.

Could what I described be done within other files, such as just the right init.rc?

Oh, you betcha. I didn't mean to take away one iota from other great devs like flex, just banged out the easiest example I knew to explain the circumstance. (I've been building unix init scripts for over 25 years, I mentioned freeza as an example of the new breed that leaves us dinosaurs laughing at our old tricks.)

As for the the rest with flex's work - please ensure that you're running U9RC9T18 of V6, and then back out whatever may conflict with your chosen rom dev.

Flex is a pretty cool guy and eh doesn't afraid of anything - drop him a line with the startup issue, and if in doubt, link him to my posts here.

No doubt, if his uber-busy schedule allows, he'll help with the right magic beans for a startup from his rom - or help you know why his way is best for his rom. ;) :)
 
thanks! I've just decided to indulge the flashaholic tendencies and I'm moving over to the mean rom for a bit. he's included init.d capabilities, it seems.

these first adopter months wreak havok on my recovery
 
I have this thing running on the stock ROM.

Based on what I've read in threads I've got it at 768hp with Nitro Lag Nullifier running. I also have SM set to run the supercharger on boot, since my ROM doesn't play nice.

Is there anything else I should do?
 
CYNICALifornia said:
I have this thing running on the stock ROM.

Based on what I've read in threads I've got it at 768hp with Nitro Lag Nullifier running. I also have SM set to run the supercharger on boot, since my ROM doesn't play nice.

Is there anything else I should do?
Click to expand...

Yes, you need to use the file I provided here, just a few posts above -

http://androidforums.com/showthread.php?p=4569101

Be sure to look at the notes there, ask questions.

What rom are you on?
 
You must log in or register to reply here.
Back
Top Bottom