[HTC EVO 3D] mpgrimm2:
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.

Credit for the post_boot.sh goes to Southern7. See his original thread elsewhere.

---------------------------------------------------------------------------------------------------------------------------------------------------------------

I've attached the version of S7's v2.1 post_boot script edited for Buttered Toast v14.3 (or Anthrax v3.6.6a-mr) that I'm running on MeanRom ICS 2.6 (Sense 3.6) with the init.d/99Buttered script removed.

Script defaults:

GOVERNOR="ondemand"
SCALECUR="1080000"
SCALEMIN="384000"
SCALEMAX="1188000" <<< This value MUST be less than or equal to MAX set by Aroma!
VOLTAGE="UNDER"
MP_SCROFF="486000"
MPGOV_SCROFF="conservative"

GPU3D_ON="320000000"
GPU2D_ON="266667000"
VSYNC_ENABLE="0" <<< Vsync is off
HW_VSYNC_MODE="0"
BACKBUFF="4"

My install routine for this using EsFileExplorer (or similar) with "root Explorer" & "Mount File System" enabled.

Option 1: (basic post_boot & Kernel Tuner. This should work for any ButteredToast Version)

- Go to /system/etc/init.d and delete everything in there except MeanRom's "99WifiWatcher."

- Go to /system/etc/init.qcom.post_boot.sh file and delete it as well

(I move them to sdcard or rename it with a .bak extension).

- Install/copy/paste "Basic" Post_boot.sh file in place of MeanRom's init.qcom.post_boot.sh file that you removed previously to /system/etc/

(double check to make sure it is renamed/named EXACTLY: init.qcom.post_boot.sh )

- Wipe cache/dalvik, Flash your custom kernel, reboot. let it sit 5mins or so. Reboot again.

- Load up the Kernel Tuner app and use it to verify all your settings took.

NOTE: you can stop here if you don't want to use the modified S7 post_boot.sh script (the Kernel will install an init.d/99Buttered script). You can make changes using kernel tuner.

If you can't get a stable setup with option1, then there is something else going on with your setup and there isn't any point in continuing

-----------------------------------------------------------------------------------

Option 2: (S7 Post_Boot & edited init.d scripts. Currently using)

- Go to /system/etc/init.d and delete everything in there except MeanRom's "99WifiWatcher."

(it keeps wifi active when the screen is off and at "night")

- Go to /system/etc/init.qcom.post_boot.sh file and delete it as well

(I move them to sdcard or rename it with a .bak extension).

- Install/copy/paste the " init.qcom.post_boot v2.1 mpg v3.6.6a.sh " file in place of MeanRom's init.qcom.post_boot.sh file that you removed previously to /system/etc/

(double check to make sure it is

renamed/named EXACTLY

: init.qcom.post_boot.sh using EsFileExplorer)

- Wipe cache/dalvik, reboot. let it sit 5mins or so. Reboot again.

----------------------- TO MAKE CHANGES --------------------------------

** open system/etc:/init.qcom.post_boot.sh file (S7's v2.1 edited for 3.6.6.a) and edit your max clock, etc as needed in the "user" section.

I think the only change to mine is: SCALEMAX= 1620000 (1.620Ghz); GOVERNOR= Lagfree;

- reboot, check with dual-core app to see if changes are active (ie Vsync is Off). You can verify init.d scripts are active by going to /data/meanRom.wfi and open it. Should show a current date & time for the last reboot when the file was started.

********** Note for Atx 3.4.6/3.5.x/3.6.x or Buttered Toast v14.3 and later? kernels **************

The Max CPU Clock (ScaleMAX) table is limited by the Aroma Kernel Installer. So if you set your max in Aroma to 1.512Ghz, you won't be able to adjust it to 1.620Ghz with ANY APP OR SCRIPT.

You have to reflash the kernel if you want to go higher, but you may bootloop if your phone can't handle it (ie with the faster FSB on 3.4.7 and up, my phone won't go past 1.620Ghz). This was done by cg for stability with the "Current" cpu clock.

- Also, make sure that when you make changes to S7's post_boot script that you keep the Max Clock higher than (or the same) as the "current" clock value, not lower.