yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Deliquified:
Just FYI, your 3.4 link appears to be the AT&T version..
[Verizon Samsung Galaxy S III] ktoonsez:
****, thanks for catching that :D. Its fixed now.
[Verizon Samsung Galaxy S III] Deliquified:
NP bro.. Thanks for the kernel update!
[Verizon Samsung Galaxy S III] brandoncarlson33:
So can Verizon use it?
[Verizon Samsung Galaxy S III] ktoonsez:
I fixed the link, just referesh the page to get new link and make sure file has VZW in it :highfive: :good:
[Verizon Samsung Galaxy S III] brandoncarlson33:
Thanks! Your da man
[Verizon Samsung Galaxy S III] Addiso:
Put this kernel on my cousins s3 and he's on 4.1.1 thought it'd be bad but booted up and working just fine :thumbup:
[Verizon Samsung Galaxy S III] ktoonsez:
Yes, the kernel is made to be compatible with 4.1.1 and 4.1.2 :good: :highfive:
[Verizon Samsung Galaxy S III] mindflayyer:
I can't seem to get my CPU core speed anymore.. I just get this message.. any ideas?

Swyped from my kernelized carbon
[Verizon Samsung Galaxy S III] luis86dr:
Try updating Busybox.
[Verizon Samsung Galaxy S III] mindflayyer:
I just installed busybox pro (pushed the latest version), installed carbon 1.7 stable release, rebooted and attempted the terminal commands immediately. Still no luck. Thanks luis for your attention. You've been helping me out with all my questions today. I appreciate it.

Swyped from my kernelized carbon
[Verizon Samsung Galaxy S III] luis86dr:
Did you update busybox then install new Rom? If so I'd update after Rom install. Judging if that's how you tried from your post. Flashing a new Rom will undo your updated busybox.
[Verizon Samsung Galaxy S III] mindflayyer:
I installed the update then busybox.

Swyped from my kernelized carbon
[Verizon Samsung Galaxy S III] brandoncarlson33:
Another awesome update! Thanks KT!!!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I have the same thing happening with another guy in the Fast, nominal, or slow cpu thread. He's using an AOKP nightly and another kernel but having the exact same issue. I wasn't sure what else to suggest in that regard.
[Verizon Samsung Galaxy S III] mindflayyer:
It worked before flawlessly when I was using the 3.0 kernel. I'm tempted to just flash a backup and run the command lines. Once I know, I'll know. :p

Update edit: I broke down and flashed an older version of carbon with the 3.0 kernel. The terminal command worked fine. All that work just to see that I have another nominal processor. :o
[Verizon Samsung Galaxy S III] WhammyDroid:
Is it possible to get the original Samsung splash screen in a zip file to flash? No disrespect to the developer , I am just not a fan of the newer splash screen.

Thanks
[Verizon Samsung Galaxy S III] prototype7:
It's inside the kernel, there's a thread in either general or themes and apps with a zip that'll change it for you.
[Verizon Samsung Galaxy S III] Casper34:
http://xdaforums.com/showthread.php?t=2096148

Found this one. Just download, reboot into recovery, flash, and reboot.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] BrUhNiGGs:
What does the new faux sound do?
[Verizon Samsung Galaxy S III] Casper34:
Update, also has poweramp control. You must update your kernel to the latest in order to use it though.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] axne1:
Faux sound is Goooooood!

EC Nationals

Wisconsin State Champs 2012
[Verizon Samsung Galaxy S III] picarito:
if i want faux audio do i donwload the foux sound from the play store?
[Verizon Samsung Galaxy S III] Casper34:
Yep. Its separate from the kernel.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Is it okay to use faux sound with acid installed?
[Verizon Samsung Galaxy S III] axne1:
This kernel hands down is banging!

Sent via Liquid 2.3/KT Fire!

Tapatalk 2
[Verizon Samsung Galaxy S III] Casper34:
Can't help you there. I am almost positive that there is a thread someplace for faux sound. I am sure you can fine your answer there.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] PoLoMoTo:
Has anyone had any luck with this on the PACman rom? If I try to set the max MHz to 2108 in KTweaker it kernel panics and reboots but 1998 works fine. Also everything is incredibly unstable, Nova randomly stops responding and wont restart, Real Racing 3 will also randomly stop and refuse to reopen, and KTweaker sometimes refuses to start as well. In candy crush there are tons graphical glitches making it unusable (all the candies are purple boxes) not sure if thats kernel related but it was working fine before flashing KT747. Thanks in advance.
[Verizon Samsung Galaxy S III] Sinker1345:
There was a math error in older kernels, long story short 1809 is the old 2108. Most phones won't handle anything above 1809. If you read back a few pages there is a more in depth explanation.

sent from my SCH-I535 running clean rom 6 and ktoonse kt747, powered by a lemon.
[Verizon Samsung Galaxy S III] Casper34:
Running it fine on PACman. I have had it on here for about 6-8 weeks now. I only update when there is a major change I either the rom or kernel. But like the post above me, there was a math error and most phones wont handle the max. Just take a down a step till your stable. I dont go above 1548.... im setup for battery life.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] PoLoMoTo:
So the 2108 setting was a lie and it has been doing 1809 this whole time, except now its been corrected and found that the phone can't actually handle 2108?

---------- Post added at 03:26 PM ---------- Previous post was at 03:22 PM ----------

I have mine setup to go into powersave and back down to 1GHz when screen off to save battery, I've found I can get two days off one charge with this setup
[Verizon Samsung Galaxy S III] Sinker1345:
Yes, that is correct from what I have been reading

sent from my SCH-I535 running clean rom 6 and ktoonse kt747, powered by a lemon.
[Verizon Samsung Galaxy S III] ktoonsez:
It wasnt a lie, it was a math error that ALL dev's kernels had since the beginning that nobody caught until recently.
[Verizon Samsung Galaxy S III] uberbdon:
Latest Kernel running great on Beans v15. Battery life much improved for me.
[Verizon Samsung Galaxy S III] keynith:
Hooah to that. Vast improvements for me.
[Verizon Samsung Galaxy S III] Rinkle McBally:
What do you recommend for gov and scheduler on liquid 2.3? I know someone has a great setup
[Verizon Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5.5.2013

1. JB_2.5.04.02.02.040.288 from codeaurora.org

2. Couple of USB patches

3. Couple of display driver updates

4. Totally sync'd with CM

5. Do NOT flash this if you are allergic to AWESOME

I WILL BE TRAVELING FOR NEXT 2 WEEKS FOR WORK AND WONT BE ABLE TO BE VERY ACTIVE DURING THE DAY.
[Verizon Samsung Galaxy S III] masri1987:
Safe travels. What's the first point in the update mean?
[Verizon Samsung Galaxy S III] Stranger_84:
Have fun traveling bro
[Verizon Samsung Galaxy S III] bb4arson:
I am not allergic to AWESOME which is why I have been on your kernel since day one :thumbup:
[Verizon Samsung Galaxy S III] brandoncarlson33:
Just when you think things can't get anymore awesome ....BAM....nice going KT.. And thanks!
[Verizon Samsung Galaxy S III] axne1:
Running like a Champ!

EC Nationals

Wisconsin State Champs 2012
[Verizon Samsung Galaxy S III] syde1020:
Can someone link me to the newest version of the crossbreeder mod, I'm having troubles finding it.
[Verizon Samsung Galaxy S III] Wi1son:
I think this is it.....

http://xdaforums.com/showthread.php?t=2113150

Sent by i535 with CarbonROM & KT747
[Verizon Samsung Galaxy S III] tbgreen89:
I'm on Slim Bean 5 which uses 3.4.41 kernal.. your latest is 3.4.43.. it won't work cause the rom is using an older version right?
[Verizon Samsung Galaxy S III] PoLoMoTo:
I know I was just joking
[Verizon Samsung Galaxy S III] jzd5032:
It works great on slim 5
[Verizon Samsung Galaxy S III] glman1:
It will work. What matters is that Slim Bean is 3.4 and KT747 is 3.4. As long as both are 3.4, you'll have no problem installing KT747.
[Verizon Samsung Galaxy S III] OneFast3:
Anyone running the latest version on latest AOKP (5-6)? I have not been able to run this kernel in awhile now on AOKP. Even when I try full wipe, once I flash this it will boot and if left alone it reboots then locks up. Has lots of FC's if mess with right after boot and then lots of reboots or lock ups. Tried the force close and clear app, no difference. Tried to raise voltage still same results. Have not tried older versions but didn't think it would matter.

In just at a loss on where to go from here.
[Verizon Samsung Galaxy S III] mikejr83:
Does the kernel have the cifs module? I'm getting an error try to use cifsmanager. "Invalid Argument" error, to be specific.

I'm assuming I need cifs.ko but not sure where to get it.
[Verizon Samsung Galaxy S III] xdapadogx:
Toonsez, I'm using the touch version of your kernel. I can't seem to find the qosmgr file to rename in the system/bin directory. Have you taken it out or am I overlooking?
[Verizon Samsung Galaxy S III] jamesino:
The newest 5/05 is working great with carbon rom. thanks!

In the future, if we decide to go with a different kernel, is there any to still get the Trinity Colors color correction?
[Verizon Samsung Galaxy S III] gadget069:
Do I change this file before or after flashing
[Verizon Samsung Galaxy S III] Jarheadflip:
After, use root explorer to change then reboot
[Verizon Samsung Galaxy S III] gadget069:
Is it safe to flash a different boot screen?
[Verizon Samsung Galaxy S III] Sinker1345:
I have flashed multiple kernel boot screens via tkmod and multiple actual bout animations via clean rom zip and rom toolbox. The only thing you'll need to do is apply the bit animation fix if you don't get a boot screen. You slums only need to do it on the first install of the kernel if you don't get one.
[Verizon Samsung Galaxy S III] gadget069:
Not finding a boot animation fix.
[Verizon Samsung Galaxy S III] Deliquified:
If by different kernel you mean different version of Linux (ex; 3.0 vs 3.4), there should be no reason why it shouldn't stay in the kernel. KT simply forked the code from a different kernel and incorporated it into his own. To clarify, forking means to borrow/use code (with credit of course) to better your own code. Nearly all things done in Linux has forked code from others. Open source and sharing is what makes Android so great. [/end tangent]
[Verizon Samsung Galaxy S III] Sinker1345:
The bout animation fix is in the tkmod zip, it's an option in the atoms installer
[Verizon Samsung Galaxy S III] mw86:
In case users didn't knkw what you meant to type, yes the boot animation fix is a selectable option in Tkmod.zip flashable in custom recovery which uses a aroma installer to make selecting your own preferences easy and straight forward and additionally can restore any option you modify, minus the boot animation fix as i think its not reversable without flashing rom or kernel or something again... Cheers! Lookup team Kernelizers if looking for the threads :D
[Verizon Samsung Galaxy S III] jamesino:
Using KTweaker:

If I set the Max CPU clock speed of my screen off profile to be the same as my mininum CPU speed (378 Mhz), will this really save my battery when my phone is idle with screen off?

The only thing that really runs in the background on my phone are the occassional Gmail and Dropbox photo syncs. One on hand, by allowing my phone to use the full range of clock speed, it can complete the necessary tasks faster and go back to deep sleep faster. But on the other, by restricting the clock speed to a low speed, it's using less battery while running but for a longer time.

Which scenario is best for saving battery?
[Verizon Samsung Galaxy S III] zeus33:
http://xdaforums.com/showthread.php?t=2144004
[Verizon Samsung Galaxy S III] gadget069:
I deciphered what he was meaning and did a search and fround the zip, i did have the phone reboot on its own after flashing the fix, but fine since then.
[Verizon Samsung Galaxy S III] luis86dr:
Edit:

Wrong thread. Deleted. Lol.
[Verizon Samsung Galaxy S III] jamesino:
Not quite sure where the answer is.
[Verizon Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5.9.2013

1. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.295 from codeaurora.org

2. ARM: 7467/1: mutex: use generic xchg-based implementation for ARMv6

3. Revert "ASoC: msm: Support independent left-right channel volume cont

4. Revert "arm: mm: Add VM_ARM_EMPTY_MAPPING flag to mark the PMD gaps

5. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.292 from codeaurora.org

6. Couple patches for schedulers main code

7. Raise MDP bandwidth requirements (this should get rid of the screen flicker that some were getting)

8. Compiled with latest Linaro

9. Linux 3.4.44

10. Completely sync'd with CM
[Verizon Samsung Galaxy S III] brandoncarlson33:
Another kick a** update , way too go KT...

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] arathorn4:
Just tried flashing this kernel for the fourth time with Liquidsmooth's latest since the mess from mid-March and again no boot after install. I'm moving on and not looking back at this kernel; frustration is an understatement.
[Verizon Samsung Galaxy S III] Stranger_84:
I'm running both just fine so it seems its a user issue ... Not a kernel issue
[Verizon Samsung Galaxy S III] jamesino:
I can't think of a reason why that wouldn't work. I'm assuming you clean flashed everything right? The latest Liquid (2.3) should be perfectly compatible with this kernel.

I'm running the Carbon 4/20 nightly myself and it works pretty well.
[Verizon Samsung Galaxy S III] Taykiin:
Just make sure you're flashing the 3.4 Linux version as opposed to the 3.0 version. Should work just fine bro...
[Verizon Samsung Galaxy S III] arathorn4:
Yeah just tried the 3.4 version...wiped cache and dalvik and even tried fixing permissions which seized up on me, even in recovery. Ugh. Had to use nandroid
[Verizon Samsung Galaxy S III] tprophit:
iirc, there was a carbon nightly around then that was 3.0
[Verizon Samsung Galaxy S III] mirrin:
Just updated from one of your older ones to the latest 4.1.2 kernel now when my phone sleeps I need to pull the battery because the screen won't come back on. The 5/3 kernel is what I was running the ROM I'm on is plasma 8 based off the latest Verizon ota.
[Verizon Samsung Galaxy S III] thornev:
I run Plasma8 with the 5/3 KT747 kernel, no problems. Plasma8 is based on the MB1 Verizon update. How can I help? (Besides teaching you punctuation :) )
[Verizon Samsung Galaxy S III] ktoonsez:
Probably too much UV.
[Verizon Samsung Galaxy S III] axne1:
Up and running smooth. :):thumbup:
[Verizon Samsung Galaxy S III] arathorn4:
Yep exactly and carbon was awesome before then. Ah well.
[Verizon Samsung Galaxy S III] mirrin:
I don't think it was. I tried resetting to default settings in ktweaker first thing. I re downloaded and flashed in the latest cwm touch. This time I wiped davlik and fixed permissions so far it is working great...

Anyway issues resolved for now.
[Verizon Samsung Galaxy S III] savagebunny:
Got the black screen right now. Tried to flash 5-9 and Boots to where my lights light up at the bottom, menu and back button, but no boot. This happens to me on 5-9 and 5-5. I swear I can't update to anything besides keeping 4-11. on LiquidSmooth v2.2 also

EDIT: Flashed 4-11 3.4 again, everything works fine again. Why can't I use anything besides 4-11?
[Verizon Samsung Galaxy S III] tihsllub:
Did you format your system factory reset before flashing the newer kernel?
[Verizon Samsung Galaxy S III] savagebunny:
No. Every phone I've had since the first Incredible I've NEVER had to do a factory reset. Just wiped cache/dalvik/fix permissions after I flashed the kernel.
[Verizon Samsung Galaxy S III] ktoonsez:
Because there was critical display driver updates made to this kernel that are obviously not in the ROM you are using. You will be stuck on 4-11 if you keep using that ROM or you can switch to a ROM with the latest updates built into it :good:
[Verizon Samsung Galaxy S III] tihsllub:
Are you trying to flash on top of ls v2.2? The new KT kernel only works with the last 2.2 nightly and the newer v2.3
[Verizon Samsung Galaxy S III] savagebunny:
Ah okay. That explains it. I did see LiquidSmooth did update to v2.3 and guys are using your 5-5 and 5-9 builds. Will check it tonight. Heading to Santa Ana for today. Repo car auctions and cheap gov vehicles for sale!!
[Verizon Samsung Galaxy S III] tihsllub:
I'm on the 2.3.2 nightly with the 5-9 kernel. Runs good but the boot splash is a little gawdy. I will mess with it in a little bit.
[Verizon Samsung Galaxy S III] xprog:
Love the kernel, thanks for your work.

I do have a feature suggestion, what about a max mhz profile when on charge, I'd like to overclock when it's on charge since eating the battery wouldn't be a problem then. Torrents/video rendering with hdmi out/GPS with music streaming/etc. I tend to do heavier tasks when I plug it in and overclocking only then could be useful.
[Verizon Samsung Galaxy S III] mw86:
Ive thought of a seperate on charge max mhz myself, interesting not sure its easy implementation but would be a cool option. Mind you heat builds when using the phones hardware actively while plugged in so having the thermal control set would probably be pretty important if this came to be.
[Verizon Samsung Galaxy S III] jakereeves31:
Why do you guys think it is that whenever I try to use this kernel it makes my games go crazy? It's not like a flicker, it's like everything just like bulges for a sec or something. And sometimes, like when I play mini golf match up, the ball just starts flying everywhere. Haha. It only happens on this kernel
[Verizon Samsung Galaxy S III] CykloneFij:
I see several references to a 5/9 KT, but can't find anything anywhere besides 5/5 release. Searched everywhere, and can only find an AT&T kernel that is 5/9/2013. :confused:
[Verizon Samsung Galaxy S III] axne1:
Page 331 man :rolleyes:
[Verizon Samsung Galaxy S III] CykloneFij:
Ugh, thanks. Searching using 5/9 and 05-09. My bad, and should have gone back more pages :eek:
[Verizon Samsung Galaxy S III] masri1987:
anyone mess around with smartassh3?
[Verizon Samsung Galaxy S III] Androideka5:
I've tried it. For me it sticks at max freq after about 30 seconds, regardless of the settings
[Verizon Samsung Galaxy S III] clothednblack:
Ktoonsez is the man
[Verizon Samsung Galaxy S III] masri1987:
That's weird. Works great for me, I was bumping music through bt for an hour and for its entirety it stayed below 486mhz
[Verizon Samsung Galaxy S III] brandoncarlson33:
I second that!!!!!

sent by a custom s3 powered by liquid smooth ROMs ,KT747 kernel with mods by team Kernellizers , themed by blackout1911 and modded by everyone!
[Verizon Samsung Galaxy S III] masri1987:
agreed

!!!

FYI, huge diff between battery life on 5\5 and 5\9

in the positive lol
[Verizon Samsung Galaxy S III] TheDriller:
I need this in a TW version.... ⓢⓣⓐⓣ :)
[Verizon Samsung Galaxy S III] savagebunny:
Come to the dark side... We have candy :good:
[Verizon Samsung Galaxy S III] TheDriller:
Lmfao. ^ This seems legit...
[Verizon Samsung Galaxy S III] Turin87:
If I want to flash an updated version of the kernel, say the 5/11 version, and Im coming from the 4/11 version, do I need to do anything prior to flashing? Can I just dirty flash? Do I need to wipe afterwards? Im still on the same ROM and have not changed anything else.
[Verizon Samsung Galaxy S III] savagebunny:
Go into Ktweaker in Apps on your phone, Force Stop, and Clear Data. Boot into recovery, flash kernel, wipe dalvik/cache/ fix permissions. Then your good to go
[Verizon Samsung Galaxy S III] Turin87:
Thanks!

---------- Post added at 09:44 PM ---------- Previous post was at 09:24 PM ----------

Just reading back a few pages and saw that there have been some issues with booting into a black screen. Apparently this is due to a display driver update that was recently released. I am on synergy's r484 released on 4/20. Is this recent enough to think I wont encounter this issue? Does anyone know for sure? And what would be the best way to see if the rom and kernel are compatible, other then flashing it of course, lol?
[Verizon Samsung Galaxy S III] savagebunny:
Ya that was my same issue I had. I gotta update to a new rom but I'm lazy atm.

What I would do is check the change logs of the ROM itself, if it doesn't say anything then ask in the thread about the display driver update and see what the devs say about it

Or simply check the Synergy thread and see if anyone is flashing 5-5 or 5-9 on the r484 build
[Verizon Samsung Galaxy S III] tihsllub:
Don't flash the new kernel u will get black screen.
[Verizon Samsung Galaxy S III] Turin87:
Ok I guess I will wait for a new Synergy build, if that ever happens. Seems the devs are working with the S4 at the moment, which is understandable. Thanks for the assistance. Glad I asked about the new build. Havent experienced any issues since I entered the mobile hacking (not sure if it is really hacking or not) world a few months ago because I have been vigilant about researching potential complications. Might have a stroke if one actually occurred.
[Verizon Samsung Galaxy S III] Mystique:
Hey all,

I just got my wife a GS3, loaded Synergy and KT..

I just saw the last few posts.. are there problems with the latest build?

.. as long as I'm here..

I set the minimum cpu value to 81, maximum cpu to 1.35.. and the scheduler to wheatley.. scheduler to sio..

Anything wrong with that?

Would that get the device through the day?

Thanks in advance..
[Verizon Samsung Galaxy S III] Maphack:
I've learned a lot because I have taken some "risks" (which are usually the result of stupid human error while flashing). I think learning to solve these arguably inevitable problems is rather valuable.

Except, in the past two weeks, I've had to do two full data wipes trying to switch from pacman to paranoid and trying to go from paranoid back to pacman. Really strange; I did a factory reset and wiped both caches and after the first mishap I formatted /system.

I guess the reason I'm posting is because I always use this kernel and I'd always get stuck at the kernel loading screen...whether it is this one or the one from the new ROM I flash.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] siriusgamer:
Has anyone tried flashing this with AOKP JB-MR1 milestone 1? When I did, the phone seemed to boot up fine, I saw the kt747 splash image but everything after that didnt show up. The screen was black but the back and menu buttons still lit up.
[Verizon Samsung Galaxy S III] tihsllub:
What's the kernel version of the ROM? Is it an early version 3.4?

Sent from my ...........
[Verizon Samsung Galaxy S III] airmaxx23:
I'm on the unofficial 5/7 cm10.1 build, the 5/5 and 5/9 kernel is causing a lot of reboots for me. I'd grab a logcat but I'm not sure how.
[Verizon Samsung Galaxy S III] ktoonsez:
U need to update to CM from 5/9 or newer.
[Verizon Samsung Galaxy S III] airmaxx23:
I'll try the 5/9 build but it happens on RC2 as well.
[Verizon Samsung Galaxy S III] arathorn4:
I second this
[Verizon Samsung Galaxy S III] ktoonsez:
WOW
[Verizon Samsung Galaxy S III] luis86dr:
Seriously? I've been running this kernel on both TW and AOSP for months now. Every issue aside from what has been clearly made obvious by KT has been USER related. Follow instructions and always make sure to provide information before making ridiculous posts.
[Verizon Samsung Galaxy S III] jamesino:
A few things to keep in mind if these kernels aren't working for you.

First, make sure it's the right linux version: 3.0 or 3.4. Flashing the wrong one will prevent your phone from booting.

Second, check the release dates of your ROM and the kernels. CM made a critical update on 4/19. Any AOSP ROM that merged the CM code at this point will require a ROM that was released after 4/19 that reflected this change. Flashing the wrong kernel in this case will result in a black screen.