yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] steve97ta:
Yeah ummm since details on your combo you got there lol
[Verizon Samsung Galaxy S III] LuigiBull23:
Settings:

Gmail sync and location services off

brightness = 40%

Tweaks:

Balanced Bull v3 + TK Mod + Greenify + DS Battery Saver + modded GSF
[Verizon Samsung Galaxy S III] drecu:
Anyone else having an issue with the built in mobile hotspot not working on TW?
[Verizon Samsung Galaxy S III] Chono631:
Does this kernel boast audio or give to option to like Siyah on the international version?
[Verizon Samsung Galaxy S III] WhammyDroid:
KT, could you look into incorporating this? It appears there is a memory leak in the 10.2 kernel. Another kernel developer supposedly has addressed it.

https://github.com/imoseyon/leanKern...5e8e9bec8198f6
[Verizon Samsung Galaxy S III] Deliquified:
Trying using viper4android. You can find it here

http://xdaforums.com/showthread.php?t=2191223
[Verizon Samsung Galaxy S III] Chono631:
Okay I'll give it a go, thanks man
[Verizon Samsung Galaxy S III] Rinkle McBally:
9-7 PAC nightly oc to 1674 with ktoonservative and zen stock battery
[Verizon Samsung Galaxy S III] jonathan413:
Ktoons kernel no OC..just undervolted and SLP governor
[Verizon Samsung Galaxy S III] mindflayyer:
I wish I had your signal strength!! Jeezy Luigi.. You're green all day! (Definitely a Nintendo pun in there)
[Verizon Samsung Galaxy S III] LuigiBull23:
LMFAO! post of the night! Thanks man
[Verizon Samsung Galaxy S III] soapinmouth:
Anyone have problems with the front camera freezing after a few seconds?

Also has any aosp rom or kernel managed to get stable Bluetooth? Mine always just stops playing randomly but still says it's connected to the device, then there's no way to turn it off without force closing bluetooth.
[Verizon Samsung Galaxy S III] SomeGuyDude:
Liquid 3.0 and the notta builds have both worked for me, either with this kernel or bms.
[Verizon Samsung Galaxy S III] dvaderx:
i run the latest carbon nightlies with this kernel and have none of those issues.
[Verizon Samsung Galaxy S III] savagebunny:
Quick question, just flashed the latest for 4.2.2.... Where is Ktweaker now? I don't see it anywhere

Ya well... I fixed it. I'm just acting a little loopy :p
[Verizon Samsung Galaxy S III] mikejr83:
Hey, I'm trying to merge upstream changes from cm to my fork of kt474. Is there a set of files that I should be aware of that contain the bulk of the KT customizations? It appears to me that KT hasn't been merged with upstream changes in a while.

I'd like to pick up keeping the latest cm changes merged in. If anyone has tips or wouldn't mind helping out please PM me.
[Verizon Samsung Galaxy S III] kennyho35:
Just flashed on slimrom build 1 4.3 and cannot clock past 1890...... Any suggestions? When I clock the max device just reboots.....
[Verizon Samsung Galaxy S III] unhappybirthday:
That is awfully fast for these procs. A few months ago Ktoonsez fixed a math error in the clockspeed calculation that most all kernels for the s3 suffered from. Long story short, people running at 2100 on old kernels were actually running closer to 1800.
[Verizon Samsung Galaxy S III] kennyho35:
OK so what's that have to do with the phone shutting down?......
[Verizon Samsung Galaxy S III] Stupifier:
He's trying to tell you that you should not attempt clocking past 1890.....It will cause your phone to shut down / reboot because your are torching your phone's CPU. The only reason you used to be able to go past 1890 is because of a math error in the CPU overclocking MHz calculation....
[Verizon Samsung Galaxy S III] unhappybirthday:
Your proc is not stable at that clock speed. Try the next notch lower until you find a stable speed. Samsung only guarantees it will do 1512...
[Verizon Samsung Galaxy S III] ktoonsez:
***** important *****

***** IMPORTANT *****

LuigiBull23 has done some testing with some people that were having issues with Video playback with version with the GPU voltage control and found that everything is OK as long as you stick to multiples of 25. Anything smaller and not divisible by 25 will more than likely cause problems/reboots or out right ignoring the values by the GPU hardware itself. When he came to me with this info it immediately triggered my memory about my Nexus 10 device doing the same exact thing. So in conclusion, only do multiples of 25 when UVing the GPU. I will change KTweaker to do steps in multiples of 25 for the next release.

Hope this helps some of you people out there :good: :D. And be sure to thank LuigiBull23!!!!!
[Verizon Samsung Galaxy S III] Droid316:
What if I use 24? That's my favorite number.J/k good catch Luigi.

™ Sent From My Eclipsed 4.3 Rom Running Stock Kernel With Killjoy Script Powered By 7000MAH Of Battery Power™
[Verizon Samsung Galaxy S III] LuigiBull23:
23 is mine.. Yea I know.. What a shocker!! :D
[Verizon Samsung Galaxy S III] Droid316:
Let's call it even at 23 1/2

™ Sent From My Eclipsed 4.3 Rom Running Stock Kernel With Killjoy Script Powered By 7000MAH Of Battery Power™
[Verizon Samsung Galaxy S III] teknikalcrysis:
Help phone wont boot!

I got antsy and moved to fast... just put CM10.1 on my Galaxy S 4, yes I said 4... :(

put this zip for aosp on the sdcard and flashed before I realized I downloaded a kernel for the S 3

the installation said it aborted, so I assumed it was safe to reboot

now my phone will not boot, just keep vibrating with a black screen, and cant seem to get into recovery by holding the volume up key...

I can however get into downloading mode by holding volume down... PLEASE PLEASE PLEASE HELP!

EDIT:

I have backups from today if I can just get into recovery...or if someone could help me with pushing a kernel through odin or where to go from here

I have the kernel I Used to root with that I used Odin on...but scared to flash that at risk of further damage
[Verizon Samsung Galaxy S III] TheDriller:
If you can get to download mode find a stock image and Odin back to stock. Reroot and read before flashing. 99 times out of 100 the wrong kernel won't hard brick you. But still not worth the trouble

Edit: if you can't get into recovery then the update package might have wrote something to your recovery image

Tapatalk 4 sucks
[Verizon Samsung Galaxy S III] teknikalcrysis:
could I Odin in a Recovery? I know that the Rooting Method said not to Odin the Recovery, but I didn't know if I could at this point...
[Verizon Samsung Galaxy S III] TheDriller:
You could try but my guess is that it will trip your flash counter and possibly relock your boot loader or something. Best bet is to Odin a stock no-wipe image and reroot.

Tapatalk 4 sucks
[Verizon Samsung Galaxy S III] teknikalcrysis:
FIXED! Thanks! Lesson learned...read on PC instead of phone so you can actually read what you are doing before you do it! LOL
[Verizon Samsung Galaxy S III] WhammyDroid:
ktoonsez, did you see this? Any chance of implementing it?
[Verizon Samsung Galaxy S III] jsdecker10:
am i missing something here? ...or has there really not been ONE SINGLE reply, other than my own, in this thread since Sept. 26th??
[Verizon Samsung Galaxy S III] kimber45:
[MENTION=4325945]ktoonsez[/MENTION]

I know the 4.2 Verizon version of aosp kernel will work on my d2usc, but was wanting to check with you and see if the 4.1 TW Verizon version would also work on my d2usc? I have read to many horror story's of bricked devices from flashing other carriers stuff to try before asking.
[Verizon Samsung Galaxy S III] Prack:
An update would be nice. I'm flashing cm 10.2 nightlies everyday and the stock kernel has had a ton of merges that this doesn't have yet :(
[Verizon Samsung Galaxy S III] mikejr83:
I forked KT's code on Github and started merging in the changes. It turns out that I merged using the wrong method or did something stupid as I can't get the kernel to build. Work's been pretty pressing lately so I haven’t been able to start over using a suggestion by KT.

If anyone is interested and knows about how to do cherry picks in git and would be willing to teach me a thing or two it would definitely help the process along.

Edit: Gotta give some props to aeroevan. Helped me out last night when trying to start the cherry-pick process.

Found out that I'm not a good kernel dev. First commit compiled come. After working on the second cherry-pick I can't get the thing to compile. Much harder than the merges I do at work.
[Verizon Samsung Galaxy S III] bigbear6708:
About to have an s3... logging in here so I can find this kernel next week.
[Verizon Samsung Galaxy S III] mikejr83:
Alright everyone. I think I may have figured git and cherry-pick out enough to make a workable build.

I've been pulling in merged commits from the cm-10.2 branch and building them. So far I've only encountered a few cherry picks that don't easily merge right in.

I should have an experimental build containing all the updates to the d2vzw kernel at some point today. If I can build the kernel and then have it boot on my phone I will want a few people to test it out as well. PM me if you're interested in testing the kernel that someone made who has not touched C in over 8 years. :)
[Verizon Samsung Galaxy S III] silver04v:
Im running the latest 4.2.2 AOKP nightly 8/20

IS there a kernel here that would work? I see the 4.2 one. Should that work? Anyone running that setup? Im coming from TW and havent run a 4.2.2 rom yet.
[Verizon Samsung Galaxy S III] LuigiBull23:
Yup. Just flash the 4.2 AOSP version.
[Verizon Samsung Galaxy S III] mikejr83:
Alrighty, update on the progress.

Turns out that whatever I build from my cherry pick branch is not flashable.

If anyone wants to take a look here's the repo url: https://github.com/mikejr83/KT747-JB.git

EDIT: Figured out the build problem. Spun up a new build right now. Still looking for a few good testers. PM me if interested.
[Verizon Samsung Galaxy S III] mikejr83:
UPDATE!

I've been able to figure out how to get the KT747 kernel to build and flash without bootlooping! I went for gold and created a build with all the commits from Sept through Oct. Unfortunately my testers and I got no data when flashing it.

What I'm now doing is going through every couple of commits and creating a build and flashing it to see where the commit comes up that breaks data.

What I do need is more testers!

I'm not posting the public link to the download here. Please only contact me if you can create nandroids, know how to backup and restore IMEI, and use Odin. I take no responsibility if one of these builds blow up your phone. However, I and your fellow crack flashers will be very grateful to the testers.

Thanks!

Mike
[Verizon Samsung Galaxy S III] mikejr83:
FINAL UPDATE (from me)

I decided instead of keeping updates here I'd post them to this thread: Unofficial KT747 Thread

BTW, I have verified a working build. I'm just waiting for KT to give me the OK.

Mike
[Verizon Samsung Galaxy S III] Prack:
Soooooooo official kt747 for d2vzw is dead?
[Verizon Samsung Galaxy S III] brandoncarlson33:
So......what happened to [MENTION=4325945]ktoonsez[/MENTION] ?????

sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
[Verizon Samsung Galaxy S III] LuigiBull23:
Nothing at all. He's just been really busy. I'm guessing the whole point of this "unofficial" build is to keep you guys up to date on the latest CM commits whenever KT isn't available to do so himself.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Thanks [MENTION=5082757]LuigiBull23[/MENTION] for always looking out!!!! So is this "unofficial" build gonna be [MENTION=4325945]ktoonsez[/MENTION] worthy??? Lol don't need my phone going psycho or nothin :) no disrespect [MENTION=3298802]mikejr83[/MENTION]

sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
[Verizon Samsung Galaxy S III] LuigiBull23:
I wouldn't know. I can't test this unofficial build unfortunately as I've already got too much on my plate to take care of and when I test I want to be as dedicated as they come. What I do know is that there will always be risks, especially when flashing from an unofficial source but I'm sure [MENTION=3298802]mikejr83[/MENTION] has worked extra hard with these cherry picks and merging of commits. . It's up to you to decide if wanna take the chance and flash it.
[Verizon Samsung Galaxy S III] brandoncarlson33:
Nicely said bro.... Thanks again!!!!!!

sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
[Verizon Samsung Galaxy S III] mikejr83:
God I hope not!!! I like this kernel so much that I decided to get it caught up on the CM10.2 commits so that some of the issues that have been addressed over the last month would be incorporated into this awesome kernel.

None taken! :) I wouldn't ask anyone to flash anything I build if I wasn't willing to do it myself. I tested each build on my phone and bootloop'd a lot. I also lost data... But nothing was irreversible. I will continue the same practice. I'll also be upfront and let you know that you shouldn't consider me a dev. I know how to use source control. All I did was figure out how KT builds his kernel and then cherry-pick the commits into a branch.

I wish you would've been able to test! I was fortunate to have one very dedicated tester. He was able to help me out on several issues. Please don't hesitate to help out in the future.

Let me also clarify the following, I don't want to do this forever. I'll do it for as long as I possibly can. I hope that KT's schedule clears up and he's able to continue to provide us with some awesome code. I'm not a dev and at some point there will be some merge that will goof me up and I'll not know how to fix it. Hopefully that won't happen for some time and we can enjoy having KT747 up-to-date with all the commits to the d2 kernel tree.

Also, I will be doing a pull request to ktoonsez's branch so that his sources will be update. Hopefully that will allow him to focus on adding in more awesome features for us.

Thanks!

Mike G.

BTW, KT ok'd me posting the link to the built kernel. Please see my previous post for the link to the thread.
[Verizon Samsung Galaxy S III] bigbear6708:
Just flashed over slim stable1. So far so good! Thanks
[Verizon Samsung Galaxy S III] brandoncarlson33:
I MISS [MENTION=4325945]ktoonsez[/MENTION] and his awesome kernels!!!!
[Verizon Samsung Galaxy S III] BrUhNiGGs:
So what happened to the tw love ;(
[Verizon Samsung Galaxy S III] Hans5849:
Sorry to tell you, but you're a dev now. Accept it like Luke accepted Darth as his father.
[Verizon Samsung Galaxy S III] mikejr83:
"No it can't be! It's not true!"
[Verizon Samsung Galaxy S III] ktoonsez:
Only load with CM 10.2 with date 10/19 or newer!

Change Log 10/20

1. 100% caught up with CM

2. LOTS of Linux and video/gpu updates

3. Added compatibility to 4.3.1

4. Added compatibility to PAC ROM new 4.3.1 requirements

5. Too many to list, if u want full list, Go here and its page 4-6 (October 3- 19)

6. Thanks to @mikejr83 for merging in a bunch of CM stuff the other day :D

https://github.com/ktoonsez/KT747-JB/commits/mr2?page=4
[Verizon Samsung Galaxy S III] ktoonsez:
OP Updated

Removed double post for no reason, what the heck are you doing today forum????????????????????
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Weird, I flashed this on Carbon's latest nightly (10/19) and got endless bootloops and same with dkp kernel. Flashed back BMS (10/19) and it booted up fine again.
[Verizon Samsung Galaxy S III] ktoonsez:
Then they are not up to date as CM, lots of changes in ramdisk and a butt-load in video/gpu.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Im pretty sure it is up-to-date since I flashed it yesterday and tried flashing an older ktk kernel, and bms and the screen was very, very glitchy due to the commits. The latest bms works fine and was recently synced with CM just like yours. But maybe I have to flash 10/20 nightly but too bad it takes 10 hours to download on goo :p

Will report back.
[Verizon Samsung Galaxy S III] ktoonsez:
The 3 from yesterday and day before are probably not in that ROM which should be the issue. I have about 400 people on CM since yesterday and everybody is working when on CM or a ROM that has pulled in those commits :D

Here is a link to the page with the 3 commits from this weekend:

https://github.com/CyanogenMod/android_kernel_samsung_d2/commits/cm-10.2
[Verizon Samsung Galaxy S III] Casper34:
[MENTION=4325945]ktoonsez[/MENTION]

I don't know if its the rom or your kernel, but I just updated to the latest vanir with your last update and my colors are all funky.

Also, it looks like the screen is continuing to update itself while on the homescreen.

~~~edit~~~

Well, its the rom, it was the latest nightly, 10/20. And the screen shots I took look fine now so that wont be any help to anyone. :mad: thanks for such a great kernel, I am running [MENTION=3298802]mikejr83[/MENTION] right now, till tomorrows nightly.

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Dammit, I just updated to 10/20 Carbon and it still cant run ktk. I guess Ill have to wait for another nightly
[Verizon Samsung Galaxy S III] Casper34:
Ya by the way it looks, KT is ahead of everyone's rom.

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] Maphack:
can't find delete poast
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Looks like it indeed. Just gotta be patient now :p
[Verizon Samsung Galaxy S III] ktoonsez:
[MENTION=3298802]mikejr83[/MENTION]

I had to revert the changes you made to my vzw build script. If you want your own build file, copy the one you currently have on your computer to safe place and then re-sync up with my stuff and then copy in your old file with a different name like "build_d2vzw_aosp_mike.sh" or something like that so you dont have to worry about conflicts with my file and not screw my builds up too :good: :highfive:
[Verizon Samsung Galaxy S III] Casper34:
Ya, it is a little confusing when you go to load one in, you have to try to remember whose whose and the dates.

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] mikejr83:
No worries. I figured all that CI mess, etc. would be reverted since it was different in your build environment. I'm not quite sure how to work my CI commits in and not put them in the pull request.

Anyways, thanks for updated build! I appreciate your work so much!
[Verizon Samsung Galaxy S III] brandoncarlson33:
Welcome back [MENTION=4325945]ktoonsez[/MENTION] how we have missed you! :D
[Verizon Samsung Galaxy S III] 32BitWhore:
x2.

Bootlooping on CM 10/21 nightly. No splash screen, just a quick bootloader screen then reboot. Just me?

Sent from my CM Powered Galaxy S III
[Verizon Samsung Galaxy S III] squito:
its bootlooping for me on PAC 10/21 also
[Verizon Samsung Galaxy S III] Prack:
I can confirm this does NOT work on latest 10/21 cm 10.2 nightly. Just bootloops after samsung logo.
[Verizon Samsung Galaxy S III] Casper34:
I got it to load on vanir 10/20, but the rom was bad. Was gonna try tonight on 10/21.

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] brandoncarlson33:
Bootlooped for me on [MENTION=280772]Dirty[/MENTION]Unicorns Rom as well, but from my understanding [MENTION=4325945]ktoonsez[/MENTION] is ahead of time so try again on future releases of your roms.
[Verizon Samsung Galaxy S III] Maphack:
Sorry if this is inappropriate/in the wrong place...

I won't pretend to know anything about development, so I apologize if this is (most likely is) a stupid and irrelevant question. I was wondering how a kernel can be released ahead of most every rom's capability to use it? How exactly does one compile information like that?

I guess the fact that some roms can actually use it answers my question for me...

Don't mean to spam the thread, I just am curious and like learning about things I can't really understand.

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] mikejr83:
To anyone having bootloop issues, have you tried using the latest unofficial CM10.2 build from mastamoon? I think he's building with the latest caf and qcril changes which looks like it has been incorporated into the d2 kernel source but may not have hit the main branch for the ROM.
[Verizon Samsung Galaxy S III] Casper34:
Read the post above this, or below yours.

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] Casper34:
[MENTION=4325945]ktoonsez[/MENTION]

Boot looped on the 10/21 Vanir. I would get the Samsung logo flash, vibrate, black screen for about 10 seconds, vibrate, Samsung logo... repeat. I can get back into cwm holding the combo. Maybe this helps? Looks like a few people are having the same issue.

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Bootloops on mastamoon's 10/21 nightly
[Verizon Samsung Galaxy S III] SomeGuyDude:
Bootloops on 10/21 Carbon, too.
[Verizon Samsung Galaxy S III] twistedillutions:
Im coming from BMS i wanna give this a run.. Can someone suggest a good settings. Right now im liquidsmooth 2.10 bms undervolt - 50 sio smartmax
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Checkout team kernelizer setups. What I use with this kernel is lulzactive/noop not even sure if that goes together well but its been smooth for me
[Verizon Samsung Galaxy S III] twistedillutions:
Ok thanks

In another note the kernel dnt install properly i dnt get passed thr samaung logo

Had bms wipe catche dalvik then flash kt747 wipe catche dalvik fix permission got stuck bootloop

So i got into recovery mode flash rom gapps no bms jst kt747 still get stuck on bootloop.. Any help plz

I did download the 4.3 version
[Verizon Samsung Galaxy S III] grislieber:
Won't boot on PAC nightly 10/21. - Just goes to entirely black screen and phone vibrates every couple of seconds. Nothing displays at all on screen.
[Verizon Samsung Galaxy S III] SomeGuyDude:
Doesn't seem like it's working for anyone right now. Just hang tight.
[Verizon Samsung Galaxy S III] twistedillutions:
Ok thanks for the response
[Verizon Samsung Galaxy S III] ktoonsez:
Yep you guys will have to be patient for your ROMs to catch up to the newer code.
[Verizon Samsung Galaxy S III] SomeGuyDude:
Which do work? It seems like mastamoon's cm, pa, vanir, slim, and carbon are all unable to boot.
[Verizon Samsung Galaxy S III] Prack:
I'm on the official cm nightly 10/22. How much newer can the code get.... still doesn't boot bro.
[Verizon Samsung Galaxy S III] ktoonsez:
Not sure, seen lots of people on TRUE CM working including my own phone. It was people on the fake CM ROMs is what I thought.
[Verizon Samsung Galaxy S III] ktoonsez:
Try this:

http://ktoonsez.jonathanjsimon.com/sgs3/aosp/KT747-AOSP-JB-MR2-3.4-VZW-10-22-2013
[Verizon Samsung Galaxy S III] Prack:
that's not a zip file :(
[Verizon Samsung Galaxy S III] Casper34:
I will try this tonight after work. Vanir ROM

This post was made by Vanlandi
[Verizon Samsung Galaxy S III] ktoonsez:
LOL, put the word .zip on the end like this:

http://ktoonsez.jonathanjsimon.com/sgs3/aosp/KT747-AOSP-JB-MR2-3.4-VZW-10-22-2013.zip
[Verizon Samsung Galaxy S III] Prack:
I was going to rename to .zip but was afraid you uploaded it wrong or something lol.

---------- Post added at 11:39 AM ---------- Previous post was at 11:35 AM ----------

Bootloop on official CM 10.2 10/22
[Verizon Samsung Galaxy S III] ktoonsez:
Building up another one, be up in about 5 minutes :good:
[Verizon Samsung Galaxy S III] GPS3:
Thanks KT. Like others, I have had issues with boot-looping on CyanogenMod nightlys. I tried 10/19 and 10/20 via get.cm and then gave up after the boot-looping 10/20.

I appreciate what you do for us :highfive:. Love the kernel/tweaker.
[Verizon Samsung Galaxy S III] ktoonsez:
Re-Download with the same link as before, I did find a difference in the BOOTCLASS section in the Ramdisk so hopefully this will do it:

http://ktoonsez.jonathanjsimon.com/sgs3/aosp/KT747-AOSP-JB-MR2-3.4-VZW-10-22-2013.zip
[Verizon Samsung Galaxy S III] GPS3:
I just tried it with CM 10/22. Same boot-loop issue after doing the following:

Install CM 10/22

Install KT747 10/22

Clear cache

Clear dalvik

Fix Permissions

Reboot