yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Sorry but I can't help you with this as I am on latest aosp-mr1-3.4. But my values are sticking.

Did you force stop ktweaker and clear data before flashing the update?( make Sir you didn't reopen ktweaker after clearing data and before going to recovery). I am using lvl_low:15 and lvl_high:30
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
instant reboot aplying those voltages on my device :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You might wanna find out what type of CPU you have. Make sure you have terminal emulator and busy box installed ( if you need to install terminal or busy box, reboot before following the steps)

Open terminal

Type: su(enter)

dmesg | grep PVS

You will see something like this:

1=slow

2=nominal

3=fast

As you can see in the screenshot, I have a type 3(fast) which can normally take more undervolting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
c'est bizzare...

i could take almost all your previous settings from other builds of AOKP + kt747 before christmas... but since 4.2, I can't for some unknown reason.

Sent from my toaster
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yes, I did. Also, I messed up. Meant to say that the ones that arent sticking are:

Battery_ctrl_batt_mhz_high:

Battery_ctrl_batt_mhz_low:

The level ones (30, 15) work fine, but the mhz wont stick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Anyone got a stable under volt for Pegasusq and sio 96-2100mhz settings?

AT&T SGS3

TEAM BAKED ROM Blackbean 5

Ktoonsez KT747 3.0.45 Kernel

Medical MJ supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Q:

Why don't people set their screen off profile as the lowest CPU 96MHz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rquinn19:
B(lack)SOD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Because when you make a phone call the screen turns off. At 96mhz the phone will crash during a phone call. Also, the voltage is close between 96mhz to 486mhz so it wouldnt save that much battery. In fact it vould take even more battery causr it will take more time to the procesdor to complete a task
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
96Mhz-2106Mhz

Screen off profile: 486MHz

Scheduler: SIO

Governor: Pegasusq

Kernel: kt747 9/13

Rom: AOKP 9/13

pegasusQ settings:

cpu down rate:20

cpu up rate:10

down differential:10

dvfs debug:0

freq for responsiveness:500000

freq step:9

hotplug 1_1:500000

hotplug 2_0:200000

hotplug 2_1:500000

ignore nice load:0

io is busy:0

max cpu clock:0

min cpu lock:0

sampling down factor:4

sampling rate:10000

sampling rate min:10000

up nr cpus:1

up treshold:90

up treshold at min freq:70

Under voltage values:

2106MHz - 1250mv

1998MHz - 1190mv

1890MHz - 1165mv

1809MHz - 1135mv

1728 MHz - 1090mV

1674 MHz - 1075mV

1512 MHz - 1065mV

1458 MHz - 1050mV

1404 MHz - 1040mV

1350 MHz - 1025mV

1296 MHz - 1015mV

1242 MHz - 1000mV

1188 MHz - 990mV

1134 MHz - 970mV

1080 MHz - 950mV

1026 MHz - 930mV

972 MHz - 910mV

918 MHz - 890mV

864 MHz - 875mV

810 MHz - 860mV

756 MHz - 845mV

702 MHz - 830mV

648 MHz - 815mV

594 MHz - 800mV

540 MHz - 790mV

486 MHz - 780mV

384 MHz - 770mV

192 MHz - 760mV

144 MHz - 750mV

96 MHz - 740mV

Give these a try! Worth it ￼
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
These are tailored for what? Battery life I presume as you are a battery life whore <3?

I thought you used to like noop/ktoonservative, these working out better?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I am always trying new settings, and these one are the best so far for battery life. Right now I'm using deadline with adaptive and the same voltage. I'm not a battery life whore :p I'm more a guy trying differents tweakings :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Noop and ktoonservative are great for overall battery life and performance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
I followed you advice and went step by step for my UV since the other postings caused force reboot. Good thread for general advice. Thx liltitiz $.$

AT&T SGS3

TEAM BAKED ROM Blackbean 5

Ktoonsez KT747 Kernel

Medical MJ supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
My new setting :) battery saving , good benchmark, smooth gaming and browsing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
I'm glad my UV setting are working out for so many people (up to 1728 MHz anyway). I'll have to try some more tweaking this weekend. ;)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
It is not your uv settings its the lower my phone can undrvolt, I tested and stressed each steps one by one. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
That's funny, b/c those steps are the increments i posted months ago in Ktoonsez kernel thread... Starts at increments of 10, then 15, then 20, etc.

Oh well ;)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Looks like we have similar phones. I posted other setting from kt747 ( maybe yours) earlier but they are not the same as my final uv.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
I don't see a lot of people doing this, but try putting 810mhz and below at 800mv, and the lower frequencies lower if you can. I've been running this setup since day one when uv was introduced into kt747... Just a suggestion
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Only thing is, if they are all running at the same voltage, they are all drawing the same amount of power... Might as well just set your min to 810 MHz; b/c there's effectively no difference between the lower steps and higher ones, if they are drawing the same. Ktoonsez discussed this briefly when he introduced the under clock steps, way back when. But like you said, if you can lower the lower steps even more, it'll make a difference.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Yeah, I thought about putting my min at 810mhz, but my 384 and 192 are in the 700mv range. What would be ace is if there was an option to remove frequencies, I'd remove all between 384mhz and 810mhz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bg4710:
sgs3att, task650's aokp jb build rom& ktoonsez 747 kernel

Min-96

Max-1512

I/O-SIO

GOV-SMARTASSV2

TOUCHBOOST1-1512

TOUCHBOOST2-810

Undervolted-10 across the board

---------- Post added at 02:47 PM ---------- Previous post was at 02:37 PM ----------

Also try:

Min-96

Max-2106

Ktoonservative

Sio

No touch boost

Under volt but not too because your phone won't handle it and will restart itse
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I just tried some tweaks with bfq and abyss plug. So far i get Better use of the CPU, good battery life and no lag with these settings. Try it and tell me what you get good results with your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Well! It looks like you have a fast CPU too. Maybe yours cannot take as much UV but you should be able to under volt a good amount too. But you will have to test the limit for your CPU as I did with mine. Which is a long process :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
And what are you trying to input?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Since 3.27.2013-AOSP-MR1-3.4 release, I can under volt more than I ever did before. But sometimes even between two fast CPU, there are differences in the minimum voltage on different frequencies. So maybe some of my voltages are just a little too low for your CPU needs. That's why you will have to do some testing by yourself :p

Side note : désolé de toujours répondre en anglais mais comme ça les post peuvent être utile pour quelqu'un d'autre qui ne comprend pas le français :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I've tried basically everything. Originally, I was going to input 1350 high and 1026 low. Regardless of the numbers, it always goes back to 0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Did you try to nandroid your ROM and kernel and try flashing a Linux 3.4 kernel with a ROM updated to Linux 3.4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
no problem about that as it's an english forum ;)

can you upload you ktweaker save file for your actual settings? i'd like to try them, maybe I entered something wrong... maybe it just need some minors adjustment for my device. i'd like to experiments a little more with those settings....

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
With my UV and ktooservative adjustment ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swiggs98:
@ liltitiz

The last table you attached with the freq, stock volt, your volt, etc did not match the default voltages in ktweaker. They appear almost -50mv lower across the board.

Should I consider your table or the ktweaker defaults as stock and therefore my baseline to tweak from?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
There's is 2 or 3 different default voltage tables. It goes with your type of CPU as I explained above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
yes please i'd like that

could you please make one with +100mv over you voltage table just to be sure i am able to load the settings without crashing?

it would be really appreciate! thanks ^^
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
When I following these instructions, why are my results different from those in your screen shot? Is the 1 to the far left of the new line the number I'm looking for?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Voilà ! Liltitiz'Ssettings_+100mv_ktoon+row: http://db.tt/WkmDl6fc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
No it is not that number! You need to install busy box and reboot. If it was already installed, reinstall it reboot and retry. If that still doesn't work try ACPU instead of PVS in the command line. You're supposed to get the same line with 1,2 or 3 at the end
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
I just applied -100mv on your settings and its working great so far maybe i had something wrong... maybe it was because i was on Zen instead of row... i don't know I'll test further tomorrow... my Girlfriend just got home with some St-Hub ;)

thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
Ah, that's what I missed... didn't have BusyBox installed. I did that, rebooted, ran the cmd in terminal and my number is still a 1! But this time looks just like your screen shot. ACPU PVS: 1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Trying these out (with less extreme UV), hoping to see some great results! Thanks for the upload.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Nah, I really wanna stick with 3.0 until 3.4 has been tested more. I tried a 3.4 ROM and kernel for a while and really wasnt pleased with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Running kt747 3.4 and latest task's aokp and my phone runs better than he ever did on 3.0 :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I assume your on the 3.4 Linux version correct?

This may have already been said somewhere, I haven't been on much lately but from what I've read so far on the 3.4 kernel update it sounds like it adds a lot of native compatibility for the type of system that android is built on, which could be why it runs with lower voltages.

I haven't made the switch to 3.4 yet, been on slim 2.5 which is still 3.0 based but I'll definitely be doing some testing when I get on the new kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You should jump soon! Ktoonsez released a test version today that is even smoother than the one I tested my UV with :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I got a 3, wondered why I could always seem to uv so much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I have a fast processor and my phone can not take being undervolted at lower speeds. If I go below 950mv on any frequency I start to get graphics glitches, fc's in google maps and really bad audio distortion if I use any equalizers in dsp manager.

I also don't think undervolting actually saves much battery. I'm sitting at 51% battery right now with 2:35 screen on time, 14 hours after unplugging with 950mv as my lowest voltage.

Considering that the screen is always the dominant factor in battery life, the amount saved by underclocking is insignificant in theory. It is explained in depth on this post: http://xdaforums.com/showthread.php?p=22126846#post22126846

If it works for you, that's great. But I wanted to put this out there for people who are upset over not being able to undervolt their phones. These processors already run at very low voltages. It wasn't long ago that processors ran on 3.3v or even 5v. We are talking about tiny changes here and I have yet to see someone post results comparing two identical setups, one with stock voltages and one undervolted.

Would anyone who is capable of extreme UV be willing to try running at stock voltages for a day or two and see if it actually makes a difference?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I think you are probably right about battery life, but that is never why I have undervolted. Usually I do it mostly for the heat reduction, especially when playing games and such. I might try this at some point though, still working on testing my voltages at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Guys I need some guidance I went to the Terminal and I ran the command to find out what CPU I have and my CPU is a 1 so what chart and settings do I use? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I am inclined to completely agree. I've been running ktoonsez's kernel for many months, and I've always tried to undervolt as much as possible. I have been pleased with the battery life, but since 3.4 I can't run ktoonsez's very well and have had to use task's underwear. The battery life is exactly the same and this last cycle was actually somewhat better. I'm am using different governors but I always thought interactive was more performance oriented and not geared towards battery life, which is what I'm using with the task's kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
todays version of kt747

hello,

im running cm10.1 with the newest version of kt747 for 4.2 that was uploaded by ktoonsez today..

i was wondering if someone could provide me with the default ktoonservative governor adjustment numbers, i changed mine based on liltitiz's tweaks to see if it would provide better battery life....but on my phone these adjustments made it run choppy and it wasnt as smooth as how it was with the default values...the problem is i have no idea what the default values were, i attempted to load default preferences from the main ktweaker menu but the governor adjustments remain unchanged..could someoe please give me the default settings or post them in the thread..

also could someone recommend what i can tweak in ktweaker for better battery life...im currently using 81-1512mhz with ktoonservative, row scheduler, noop on screen off, stock voltages..486mhz screen off...

---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------

im looking for detailed info on how to change the governor adjustments for ktoonservative for better battery life, and or tips on uv, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
never mind...someone has already answered my question in a different thread thanks anyway :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Alright, I finished tuning my uv and here are the new values. Got to them by turning down each voltage until a reboot/crash, then going back to the last working one (3 mins stability test) and adding 10mV just to be safe, basically the same way you did. Running another stability test against them all, and it just succeeded. Have not tried any overclocking yet, since everything is running smoothly without it for now, possibly will try to do so pretty soon. Settings as follows, settings file attached (Set on Boot disabled) (.txt extension added to allow upload)

Frequency : Stock Voltage : My Voltage : Difference

1512mhz: 1150 mV : 1070mV : -80mV

1458mhz: 1140 mV : 1040mV : -100mV

1404mhz: 1140 mV : 1010mV : -130mV

1350mhz: 1125 mV : 990mV : -135mV

1296mhz: 1125 mV : 970mV : -155mV

1242mhz: 1100 mV : 950mV : -150mV

1188mhz: 1100 mV : 930mV : -170mV

1134mhz: 1075 mV : 910mV : -165mV

1080mhz: 1075 mV : 890mV : -185mV

1026mhz: 1025 mV : 880mV : -145mV

972mhz: 1025 mV : 860mV : -165mV

918mhz: 1000 mV : 840mV : -160mV

864mhz: 1000 mV : 820mV : -180mV

810mhz: 975 mV : 810mV : -165mV

756mhz: 975 mV : 800mV : -175mV

702mhz: 925 mV : 795mV : -130mV

648mhz: 925 mV : 785mV : -140mV

594mhz: 900 mV : 775mV : -125mV

540mhz: 900 mV : 750mV : -150mV

486mhz: 875 mV : 740mV : -135mV

378mhz: 850 mV : 720mV : -130mV

189mhz: 850 mV : 715mV : -135mV

135mhz: 850 mV : 715mV : -135mV

81mhz: 850 mV : 715mV : -135mV

Other Settings:

OC: Off (For Now)

Lock Frequencies: On

Min: 81 MHz

Max 1512 MHz

I/O Scheduler: row (no adjustments)

CPU Governor: ktoonservative

Governer Adjustments:

boost_2nd_core_on_button : 1

boost_cpu : 1134

boost_gpu : 0

boost_hold_cycles : 22

boost_turn_on_2nd_core : 1

cpu_down_block_cycles : 22

disable_hotplug_bt : 0

disable_hotplugging : 0

down_threshold : 52

down_threshold_hotplug : 35

freq_step : 3

ignore_nice_load : 0

no_2nd_cpu_screen_off : 1

sampling_down_factor : 1

sampling_rate : 45000 (for some reason it reset to 10000, but that's what I had it set to)

sampling_rate_screen_off : 90000

up_threshold : 57

up_threshold_hotplug : 58

Extras:

Screen Off Profile MHz : 486 MHz

Disable Screen Off MHz Call : Enabled

Screen Off Profile Gov : Unchanged

Screen Off Profile Sched : noop

Bluetooth Profile MHz : Unchanged

Vibration Strength : 120

Toast : Enabled

Swipe 2 Wake : Disabled

Trinity : Enabled

Battery MHz Control:

Low : 15%

High : 40%

MHz Low : 810 MHz

MHz High : 1080 MHz

Disable While on Charger : Enabled
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Alright, 1809 is as high an oc as I can get. Can't get 1890 to stop hot rebooting so that is the best I can do. Voltages for those steps below with new settings file (Set on Boot off) (remove the .txt extension) Might not stay with these, if it is too warm I will probably go back to 1512.

Frequency : Stock Voltages : My Voltages : Difference

1809mhz : 1265 mV : 1230 mV : -35mV

1728mhz : 1265 mV : 1180 mV : -85mV

1674mhz : 1250 mV : 1140 mV : -110mV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gundamboy:
haveagr8day, your settings are amazing. Once I tried OCing it, reboots galore.

I guess I'll stick with regular speeds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
my settings are pretty much identical to yours except for the uv, i only uv'd 25mv arcross the board..and battery life has been pretty good....just out of curiosity do u know freq_3 actually does when u change it in the ktoonservative governor adjustments...and you don't change the up_threshold or up_threshold_hotplug at all? do u know what these two do and what effect increasing or decreasing the values has?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You would need to take a look a the first post of this thread there's a lot of infos ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
thank u sir.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
mpdecision file

does anyone here use the mpdecision file tweak? if so do you notice a difference in battery life and would you recommend it to other people?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Do you mean the renaming of it to kill it? I think ktoonsez has said it doesn't really affect battery life but I've seen others say it helps but as long as your on ktoonservative or another hot plugging governor it won't hurt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
I haven't deleted Mpdecision in so long I don't even remember when. And I haven't noticed any issues related to battery or performance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
thanks guys...ill probably just leave it alone then...my battery life is already pretty good no need :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey just re name it with a .bak at the end. When i did it I got a noticeable battery improvement. If you want it back just remove the .bak extension. If you forgot where it is, it's in: /system/bin.

It only takes a minute try it out. I took a screen shot of my battery graph on the day I renamed it and there was a noticeable change in slope, not a massive change, but notice able.

The left bar before the reboot gap was with mpdecision, afterwards was without. The giant drop was probably when I was in cwm.

It's a personal thing it seems, try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hey liltitiz, are you still getting like 4 hrs of screen on time? Are you on a 3.4 kernel/ROM? Also, would you mind posting a screenshot of your battery screen? Do you use wifi or data, and if so, do you keep them on when the screen is off?Thanks, and sorry for the bajillion questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
i just flashed the latest version of kt747 3.4...ill wait and check my battery stats after a day of use and then ill try renaming on the next charge to see the difference...thanks a lot i appreciate the help..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Im one of those that still deletes mpdecision. I too feel it helps with battery.

ATT SGS3 dipped in Smooth Liquid. Asswaxed by BMS.

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
I haven't deleted the mpdecision file in a very long time ever since Ktoonsez said that it really doesn't affect battery life
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Though as of right now there is no mpdecision in the ROM Ktoonsez runs on ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
no mpdecision in aokp???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Well by all means not all AOKP but specifically his setup whether he is on CM latest nightly and or AOKP he delete mpdecision every time. He had said no big deal on deleting it in past or not but now he has autohotplug as an option which means no one on KT kernel ever truly needs mpdecision. The autohotplug function added works perfect and the hot plug governors don't need mpdecision or autohotplug. :Good: :high five:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
i understand, just made it seem like AOKP doesn't have mpdecision upon a fresh flash. I dont notice a difference with/without it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Well it runs and produces a lot of log errors. It isn't really doing anything major but technically its using CPU cycles. If you look at log cats a lot its annoying to see so makes sense to just rename it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Especially on 4.2 android. If just renamed it does that but if you comment mpdecision out in init.qcom.post_boot.sh in /system/etc on line 223 where it says mp decision place a # in front to prevent it from ever launching and if it is missing the above prevents log cat flood too. Anything before android 4.2 seems to be fine deleting it or adding .bak to the file name.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Damn maybe that's what is causing my weird reboots on a different kernel. I have been deleting mpdecision and as of recent i have been having strange issues. I renamed init.qcom.post_boot.sh and my problems are gone. hmmmmm....