yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Yeah I know but I was wondering if the assigned voltages are applied if ktweaker isn't set on boot? I would guess yes since you seem onto it :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If it is NOT set on boot, no voltages are changed and it uses whatever table was selected. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

ktoonsez, where did you get 850 mV for the difference? Looking at those tables it looks like a 50 mV difference to me. Am I blind?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
I have not yet been able to get D to boot. I was one of the major strugglers with everything from the 3/27 release until today's C release. The C release booted but after about 3 hours I started having the data problems. I got C to boot by installing 3/20, booting, and then deleting the settings.dat file from within recovery and then flashing C and wiping caches as normal. Clean install seems to only work about half the time for C.

The good news is that by going through the 3/20 release, I got 3/27 to install and boot.

Is there a second place the settings file can hide? I had it persist through an uninstall and data wipe of Ktweaker. I couldn't find it in the file manager in recovery either. I did not have Ktweaker backed up. It's possible I just missed it but I wanted to check and make sure.

Thanks for all the work on this insanity over the past few days!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
I changed my voltages to those that are the "nom" and it still occurs.

Here is a last_kmsg if that helps at all

https://www.dropbox.com/s/ck3ajikwmkf661s/last_kmsg.txt.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I had the reboots on the d version. I set the voltages to stock and it still happened. Oddly, the thing that fixed it was locking the frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
EDIT: I misunderstood before, let me double check my default voltages.

EDIT2: My voltage table is the same as the guy the posted the screen grab. Let me know if there's any info I can capture that will help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM, yep your right. Fixing :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Testing this out myself..

Locked the frequencies, and quadrant ran through zero problems.

Unlocked the frequencies, ran a quadrant test; bam lockup/reboot.

---------- Post added at 08:51 PM ---------- Previous post was at 08:35 PM ----------

Another odd thing, I decided to test out some OCing, since when I had "lock frequencies" checked I didn't have any reboots. My phone rebooted after setting it at 1988 or whatever it was, and now just keeps rebooting (i assume the settings are being applied at boot) but I never told it to set those settings on boot. Any way to reset the settings? Cause I can't get it to do it without rebooting on me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks like a low voltage issue to me or somehow an app is setting a Mhz that is too high for your phone, there are no error messages at all, it just rebooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats not an odd thing, you OC'd too much and what ever kind of hotboot it is doing still has your 1988 set. Best to pull battery for 20 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Add 75 mV to all steps :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tprophit:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

My stock voltage table starts at 925, for 81mhz. Uv -75 didn't work, I've been on -55, seems to work, but battery life not that good.

Also used to oc to 1728, now at 1684.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neyenlives:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I must have a gem of a cpu, mine starts at 700mV and rises to 1100mV. It's a preordered launch device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tprophit:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I must have the slow cpu. But since kt selected the highest voltage table, I don't understand why a can't uv the same amount as before
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hey guys, I noticed that if I set my min to 81Mhz my CPU frequencies keep jumping to max then back down then back up, but if i put the min frequency to 135 it doesn't do that. I'm on Ktoonservative/SIO. I think this only happens on Ktoonservative but I may be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Well selecting "lock frequencies" have been helping me with lockups.

Also using the "fast" voltage table, the ones with the lowest mV being 850mV, and no problems. Kinds seems like whatever locking the freqs does is helping me out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Because I did NOT select the highest table, that was the old kernel, but thinking Im gonna go to the static table again and see what happens. Everybody was used to it anyway and UV all they want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Happens on all govs, its too low for most phones/ROMs but people like choices :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Cool, what it does is locks out all apps from changin the min/max Mhz, simple as that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neyenlives:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Just lowered voltage tables again by - 25mV across the board. So 700mV to 1075mV (81-1512Mhz)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AOSP 4.2 Linux 3.4 TEST "E"

Another test, this one has 1 static table that is forces to everyone's phone (nominal table) and a few patches for thermal throttling that may have been issuing a 2106 Mhz. Justin this might be your winner here, Ill keep my fingers crossed:

http://www.mediafire.com/?mec769waj60685d
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
KT I can test whatever you need, pull logs, etc, but I also have a phone that will run anything it seems, so I may not be much help...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks buddy, but ya I need someone that cant run it so I can see whats going on :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Should we wipe KTweaker data for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Test E unfortunately does not work for me so far D is the best for my device :good:

EDIT : I deleted KTweaker data and it is working good on test E ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Couldnt hurt, but none of these releases today needed it unless you were coming from the 3/20 kernel or older.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tprophit:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Thanks, bear with me, I'm trying to understand. Looking at the two voltage tables, and comparing them to my voltage table, it seems my phone, or the kernel, selected that (higher) voltage table, which makes sense, because I ran the cpu test, and the result was either slow or nominal; I know it wasn't fast.

So, once the voltage table is selected, is that it, or is there some condition that would change it?

If there are different processors (fast, nominal, slow), it is genius that you wrote a voltage table for each that applied. Are the processor differences non linear, and the reason for not being able to uv across the board?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
As far as I can tell from looking at the code way back, it reads a bit from the hardware and decides on the best table for your specific device ONE TIME at kernel initialization. It uses a low level "read hardware" call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Got a last_kmsg or did you already boot again after auto reboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Running the original 3/27 3.4 with Task's 3/27.

It has been butter until tonight.

Suddenly, everything got fairly laggy. I tried changing gov/sched, but it didn't help.

Saved the logcat, rebooted, and the butter came back.

I've linked the laggy logcat. I hope this helps!

https://www.dropbox.com/s/fookz4tpn4vo5lb/2013-03-30-00-48-26.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sorry man, but logcat is ROM, dmesg is for kernel. Anyway, it was most likely a memory leak in the ROM, Ive said this before 3.4 is stil an infant and needs time to work things out :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
E has been the closest after C to working. It actually booted all the way up but only for 3 seconds before boot looping. Every time it was booting all the way up but as soon as I unlocked it and tried to open any sort of file explorer to get you the last_kmesg it would lock up and reboot. I'm going to reclear all the data and su permissions and try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Best to do it with your PC if your having that much trouble :good:. With a PC you can also poll things like:

adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

and

adb shell dmesg

you can download this and extract to your PC and open a command prompt in that extracted folder to run those commands:

http://www.mediafire.com/download.php?0b1b7mconuzyf27
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
I'll definitely get it tonight but my phone is blazing hot right now and I want to give it a little break. It's had a hard day. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I so totally understand that the most of you are using tasks rom but this is my third time asking for some help on the TW version of 3.27.13. I'm having the same issue as you all. Any time put into the TW version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

When I flashed D version it was constantly rebooting. Took me 10 minutes just to get to recovery. Idk if this will help. First time pulling one.

http://db.tt/rPKYV2jy

Edit: went back to 3/27. Ill point out I never had problems with it. I just wanted the newest lol. Your hard work is awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I've definitely been reading/keeping up with the thread and I wanted to share something i observed. Renaming mpdecision improved my battery life. Here's a screenshot. The first gap is the reboot after renaming

I want to know does anybody still do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

It works! Thank you kt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

.

Ya know what, I think it's the thermal throttling that's killing this kernel. I kept getting annoying boot loops after trying antutu for a moment. I let it sit and cool off for a bit and it booted up fine after that.

Temperature is a factor. Temp never bothered my phone before
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I do. Got over 30 hours last charge on my usual usage when I usually got about 24. No WiFi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Up and running. One point, I always wipe ktweaker data before flashing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
I'm one of those who had no issue with the first build.. till last night, it randomly locked and from there, bootlooped over and over. My way out was to dirty flash AOKP, go grab test D and flash it. Been good so far and probably won't jump on test E if this one is stable.

If for w/e reason I get more bootloops and I'm at home, I'll pull the required files to troubleshoot with adb.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Didnt help :(. It was the recovery's last_kmsg.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crixley:
I was having a lot of issues with the tw 27 version so I raised my voltage by 25mA per step and it seemed to have fixed it.

On reboot though it gives me a weird message about stuff not matching up to what I have saved and I have to keep clicking yes. any idea on how to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I agree. I let my phone cool off all the way on my windowsill with a full charge and e booted right up. Guess I'm flashing with a cold pack from now on :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Even before I started getting bootloops I noticed that my phone was running MUCH hotter after upgrading to a 3.4 ROM and kernel. Interesting...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
Running stable on "E" with liltitiz's ktoonservative tweaks. The biggest difference for me this time around is that I didn't OC. That and/or I only UV by -10 across the board.

KT, thanks for a great kernel and your dedication to making it work - all-time and over the past 24-48 hours!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Switched to noop/interactive and then the reboots kept happening until I went back to tasks kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Did you try the "Lock Frequencies" thing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Yes I always do I my phone wasn't so temperamental
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
having bootloops with the newest version going to flash the latest nightly and try again maybe it will help out.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AOSP 4.2 for Linux 3.4 TEST

Here is another one to screw yourself over again, FLOAM :D

http://www.mediafire.com/?p89pdeudbh7cs11

Let me know guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astroZ0MB1E:
TW 4.1 flash error

The 4.1 TW version is failing to flash. I cleared KTweaker data and forced stopped before flashing. I know this has no effect on flashing the kernel, but do you need anything from me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Dont need anything, you got a bad download and the zip file is corrupt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Gonna try this one. I still keep getting random freezes. No bootoloops or random reboots yet.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Got this thing up and running smoothly so far. :D:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

So far so good! What has changed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Page mapping patches

Disable QCACHE

Enable ZCACHE

Enable ZRAM

And a couple other patches from CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
I loved the new colors but I never was able to tell exactly how big a difference it actually made until you made it an option. It's so much better! Everything looks so yellow with morfic colors turned off. Excellent job with ktweaker! Thanks much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, ya morfic really did a great job on those numbers:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Okay, so I'm going in...new PA RC3 is 3.4 and actually comes with KT kernel, but I don't know which version of 3.4, so I'm going to flash over most recent KT build. Your settings in post 3 apply regardless of build? Going to flash non-DD S3 that currently has PA RC2 and KT 3.0. If this works well, I'll flash DD S3 with Carbon 1.6 (currently running 1.5) and this KT build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Looking good for me, only had minor issues on prior versions though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The settings kinda work for both versions. I run 3.4 so there are some things that dont exist in 3.0 that are up there but your going 3.4 so u r good. Be sure to do the procedure below:

WIPE INSTRUCTIONS

1. Go to the normal place to "Clear Data" and click "Force Stop" 1ST(usually on "Settings-> Apps")

2. Click "Clear Data"

3. Delete KTweaker from /system/app folder

4. Do one full reboot

5. Boot to recovery and flash

6. When u open KTweaker for the first time it should NOT ask you any questions, if it does, go back to step #1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astroZ0MB1E:
Cool. Maybe you're fixing it now, but when I tried to re-download it I'm getting an access denied message from the download server.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Works perfect thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

No. The file is fine. Its you internet connection at the moment, browser or mediafire
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

GOOD LUCK MAN. Hope it works. Keeping my fingers crossed :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I'm still on the original 3/27 without issue but since a few things were changed on this last test kernel, it shouldn't be an issue right? Might just smooth things out even more than they already are. Hmmm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya, I would upgrade it, got some more patches that have nothing to do with the 15% of people that are having reboot issues, so you will see some gains. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I can't live with out you're battery saving features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man, hopefully this one is the winner :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I like gains. Going to switch to the phone and download (currently posting from the tab).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Once I got my phone cold it booted right up. The last release I was starting to get random reboots after a few hours. We'll see how this one behaves.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Also on 3/27 without issues. You've released so many lately that I'm not sure which one to upgrade to! Fantastic work and support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] picklerick:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I also have constant rebooting with tw jb 4.1 3/27 kernel. I followed the wipe instructions but was forced to revert back to 3/14. I even tried setting the kernel defaults.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Was fine until driving today and tried to use GpS. I kept getting reboots and had to use Nandroid reverted all the way back to RootBox and 3.0 kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wOrHeR SvK:
many many reboots on 3/27 and also on TEST... @PACman v22.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neyenlives:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

So what's going on man? What fundamental thing changed because myself and I guess then other 15% have been using your kernel all along, every version, no problem, and now all of a sudden we can't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

The Linux 3.4 kernel doesn't play nice with every phone. I think, KT is the genius here :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Ktoonzes I'm on that 15% too :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neyenlives:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Meant to post this in the d2vzw thread, that's my bad.

Referring to TW kernel actually. But i actually tried to load the 3.4 Kernel on the Carbon 1.6 build and it didn't work either, so right now from where I sit I can't use any KT kernel after the 3-14 one. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Strange, works fine for me. My phone has been more stable than others on the new 3.4kernel though :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I've been able to get the latest tests working by removing the battery for about 30 seconds once it freezes after the initial boot (sometimes it takes a couple of times). After it booted normally, I haven't experienced any reboots so far. Hopefully this will help the other people stuck on bootloops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

That sounds like a Band-Aid though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
todays kt747 version

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...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Post #3. And you can always clear data for Ktweaker and you'll go back to defaults...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Or just select "load defaults" from the main menu in Ktweaker. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gurdsang:
thanks but where can i find post 3..sorry im new to xda
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Go to the first page of this thread and look at the third post.