yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Viper67857:
I've been seeing this on TW since 4.3 with mjb bootloader. Doesn't happen to me anymore since updating bootloader and modem to ne4.

Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
not sure what you're using..but i had to (temporarily) go to CM11 for the past month and used several nightlies (up to july21) and wifi worked just fine! this on two 747M's and a 747 (AT&T)...no issues here on 10 different nightlies...

---------- Post added at 10:23 AM ---------- Previous post was at 10:15 AM ----------

Been using your kernel(s) for few years now...swear by them...at least for many Galaxy variants..i love the advancements you've made over the months/years...great stuff.. i had a brief hiccup with some oc'ability and small stability with a few updates about 9 months ago..but resolved fast..

as long as it's functional/compatible with whatever rom im using or a friend might be using..i always recommend it as a "must" have..heck even for a few that dont want to mod..i usually can convince them to at least root and put on your kernel so that they can unlock and improve (to some degree) the blasted stock TW...and they always thank me... so thank you..

keep up the good work bud
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Try harknes kernel.. Working perfectly with latest nightly. Kernel has the WiFi did included..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
In the Most recent CM Commits, they have done away with Kernel Modules. Once that commit is included in KT, Wifi will be working again. [MENTION=4325945]ktoonsez[/MENTION] is aware of this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
[MENTION=4551784]matrixzone[/MENTION] harknes?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://xdaforums.com/showthread.php?t=2301896
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Correct me if I'm wrong but is it for d2lte? Or only t mobile?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
D2lte.. This has been running smoothly for me for the last 12 hours..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Your kernel settings?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Guys, this isn't the place to talk about another kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
I think so too, sorry!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
It is one thing to point to other kernel. But asking to be spoonfed about THAT kernel on this thread is not the proper way .You have questions on other kernels then ask it on THAT thread.

If its not a question about KT747, please don't ask or encourage here. The other kernel's thread is wide open for precisely that discussion. [MENTION=4311957]polobunny[/MENTION] you have been a very helpful and good contributor to these threads. Don't let others drag you down the wrong rat hole.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm aware, hence my simple link so the discussion could be brought elsewhere (in the proper thread). :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Just installed the latest Carbon Rom Nightly and Wifi will not turn on. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's normal and if you read earlier posts you will notice it's because kernels will need an update. This is due to a cm commit that has moved wifi from a module to embedded, to put it simply.

For the moment you can use the stock kernel until KT747 gets updated or use an older release of your rom (prior to 24th of July).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I should have been more clear. I read the earlier posts but just wanted to update that it was happening on Carbon as well. Using the, ugh, stock kernel for now. I know all the devs do this on their own time. I'll be patient. KT has been the kernel I always find myself going back to. Tried others. No comparison IMO.

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah ok, it looked like a question to me. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
In that case we page our Dev with a [MENTION=4325945]ktoonsez[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Thanks Perseus. I gave him a heads up via hangouts.

Sent via my Galaxy S3 (or 3 rather, it's more of a Frankenstein creation of the working parts)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Cannot...deal...with inferior kernel...much longer! (gurgle)

Sent from a warranty crushed i747 running Quantum. F**k Knox. That is all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joerolando2701:
Hi just flashed stock rooted att kk with latest ktoonz kernel having trouble with boot animation.zip in data local does the touchwiz kk kernel not support custom boot anymore? I ws s also previously using a flashable zip to change the splash screen when ok was using ktoonz 4.3 tw kernal which now causes a bootloop anyone with some advice to get these working again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Loren Railsback:
I'm running stock rooted Touchwiz 4.4.2 with the Ktoonsez kernel and my GPS can't lock. I am unable to use any sort of navigation, which I rely on a lot. Any suggestions? Thanks :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
[*gps fix] alternate gps fix]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
I have tried nearly every kernel and this one is the most stable one I've tried yet! Battery life has been very good too! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] emilakd:
I have problems with the proximity sensor!

when I make a call the screen turns off

any solution? only happens with the rom based on stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Hey KToonez can you throw us an update with the wifi modules?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] talkingmonkeys:
[MENTION=4325945]ktoonsez[/MENTION] speaking of wifi modules, would you know what I'd need to make the ne4 stock kernel work with wifi on old 4.3 bootloaders like you did with the nd8 kt747 kernel? I don't know a lot with kernels and I was told you might know what to do for this.

Thank you

Sent from my Samsung SGH-I747 running TMS3KK 2.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You mean without. Hehehe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Yeah that's the ticket! ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I've spoken with ktoonsez, he doesn't even use a galaxy s3 anymore and is slammed with work. very busy right now and this device is not his top priority. I will be probably syncing the code tonight with cm, Linux kernel upgrades, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hope kt reads the same
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
I have never had GPS issues with the KT kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
GPS issues? no. still trying to sync kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] talkingmonkeys:
Gps issues are usually the device itself. Try taking the battery cover off and tightening the little screws or an app like gps status and toolbox. You may need to research an nvrebuild and do it too.

Now lets get back on topic this is about the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Which wouldn't be solved by using the stock AOKP kernel, like the person is implying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Please help lol

Nothing is wrong with mysetup. I tried newest kernel and kernel from around the date of my rom. Just stays on the kt747 splash screen for hours.

Isn't the kernel domination splash only supposed to last for a second then go to normal splash screen? Its not doing that for me. Running slimkat build 6 stable. Tried kernel 6-10-14 no dice.

The **** is going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
Always do the following AFTER installing the kernel:

1. Clear cache

2. Clear dalvik

3. Fix Permissions

did this from OP ?

tried factory reset??

(MAKE THAT BACKUP!!!!!!!)

good luck. ;)

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
1. Myth

2. Myth

3. Myth

None of this is needed when flashing a kernel. Only 1 & 2 are needed when switching roms with the same base.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
thanks for the correction.

srry for misinformation.

:good:

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It happens. You're not the first one, you're not the last one. These myths have been spread for so long they're hard to kill.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Learned on my own that a kernel flash requires nothing. If I'm going from another kernel back to KT, I freeze nstools, boot to recovery, flash KT, reboot and set things in Ktweaker. I'm using Carbon, and when I upgrade I clear cache, clear dalvik, flash the ROM update, flash KT, reboot and all is well. Been doing it that way forever with no issue. I clean flash about once a month just to clean things up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I still do it. Call it what you want, it's better to err on the side of safety. Hell, I nandroid every three days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
I did that anyways still didn't make ROM boot. I know there just myths anyways. I own 4 android devices and I hardly ever do 1 or 2 or 3 unless I have an issue.

So obviously its the kernel and not me, I'm not an idiot lol I've flashed 100s of times.

Now enough arguing about irrelevant steps lol how can I fix this, or what do I need to submit to help the developers sort it out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
if you did an Odin restore and flashed your ROM and kernel without wiping in between, I found I get a boatloop no matter what. have to wipe data after Odin
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
+1^^^^^^

Yep confirmed. It is Strongly reccomended to do Factory Reset before flashing AOSP Rom After Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Thanks perseus.

EVERYBODY:

KTOONSEZ is aware of the issues we are facing. He is very busy and actually out of town right now for work. I am having some roadblocks in syncing updates with the kernel source but KT and I are talking and he will revise my terminal commands. ETA is about a day. Still, his releases are probably cleaner than mine will be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
So I take it I'm just Sol? Oh well. Good bye ktoonsez, ya treated me well!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Yeah you are man. Sorry, its like our absolute obligation to make leeching children pleased with our work so they can play uber cool Gameloft games.

I said mean things :( Sorry mods! And of course ktoonsez.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Edited.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Guys, cool off. we don't need the thread derailed. If you don't like someone's post, hit the "Report Post" button on each Post. Its that Orange Triangle Button with an Exclamation Mark inside. Its located in upper right corner Next to Twitter Icon.

A war of Words here WILL Bring in Mods and Infractions will start happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
U are correct. I'll edit my post and just report him. No need for his bull. I was simply saying goodbye. And thanking ktoonsez for the 2 years I used his kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Which Rom was it that refused to Boot on you ? Do you have the Build Date ? Also post the Build Date of the Kernel you flashed.

Last but not the least typically boot problems are caused by wrong device kernel being flashed. So please make sure that the Correct Device's kernel was flashed. That too AOSP version if you are on a AOSP Rom. Otherwise TW Version if you are using Samsung Touchwiz or based thereof.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
ROM is slimkat build 6 stable date 2014-06-03 boots fine with stock kernel.

Kernels I've tried, 06-01-2014 and 07-10-2014 both aosp kk. Wiped cache ect

Slim at has merged to d2lte I'm sure you already know that.

When phone starts to boot I see the kt747 kernel domination and it never goes away. Blue led starts pulsating. But never boots to desktop or nothing.

Some more info.

I had issues installing twrp, all my mounts were empty 0mb. I made a thread about it and ended up figuring out it was because my new phone had the newest bootloader.(END2) and twrp wasn't updated to work with it. So I ended up with philztouch. Works fine. Could my boot loader possabably be part of the issue?

I don't want to be looked at as some free loading kid, not sure wtf his problem was. I'm in my 30s and own a business and I need my phone for business. I'm wiling to donate to ktoonsez to help, if money is the issue..... Free community, didnt realize i would be outright told im worthless unless i donate. Or as he put it a leech.

Battery life is worth the money to me. Stock I only get 3h screen on. Kt747 I get 5-7 hours!

Thanks for your time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DutchDogg54:
/\ Right here's why I'm here - Edited out unnecessary language and a combative, incendiary phrase - Please keep your discussion civil and advancing of development or take it to PM's.

Perseus is correct, reporting issues is the

only

right way to handle it. Posting openly what should be handled in PM or just kept to yourself is NOT acceptable.

You made a wise decision editing your post. I do believe you were meaning to say goodbye in a nice way but there was a bit of an air of entitlement, like, "Oh, my problem won't get fixed, welp I'm outta here!" That's probably not the best way to approach development that you're enjoying for free and for which you have no claim to ownership. Just a bit of advice. No problem saying a sincere goodbye, but when you're typing out text it's hard to show sincerity without making it very obvious.

Now, let's get back to development. :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
My apologies, I've been here long enough to know that don't fly. Thanks for taking care of editing the post, perseus. Again, I just do NOT appreciate the sense of entitlement anybody may feel towards an unpaid, hobbyist developer. I appreciate the suggestion (reporting) but I don't think the guy would even notice how his comment came off. I may have misinterpreted how the comment was intended to come off as, but as you said Dutch, all we're doing is reading the text you put down on the screen, there is no tone implied. Sorry for my rude attempt at re-railing the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I don't think its a bootloader issue. But I won't rule it out. Take a Nandroid. Then can you do a factory Reset, wipe Dalvik and Cache ? since you have Philz, there's a option for New Rom do so. Once done, flash latest Slim Stable and Most Recent KT747. See if it boots at all.

Please note, in one of the more recent versions of Slim, there was a Long boot time issue. It has now been resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
If you happen to be coming from an ODIN, make sure you do a full data wipe before flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Alright, let me make sure I got this all straight.

Nandroid

In philz touch click new ROM and this will wipe everything? Or manually wipe caches and format system then click new ROM?

Then install slimkat. Wipe cache reboot then install kernel? Or skip the wipe and just flash kernel right after ROM?

Below berry mentioned about Odin and factory reset. I used unified toolkit to install recovery. And installed ROM from zip on SD card. Should I go do a factory reset before I do anything else. I've never clicked factory reset ever.

I will try this tonight when I get time. Also I would like to figure out why twrp reads all dirs as 0mb but that's another day in another thread lol

I'm not 100% clear with Odin. Do u mean if I installed a ROM via Odin? I just used unified toolkit to install recovery. Do I still need to factory reset?

i don't live in the past, so what was said was then, this is now. Life goes on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Hit the New Rom Option in Philz. That will do a Factory Reset and format the partitions. Wipe Dalvik and Cache for Good measure.(Probably redundant but just the same.) once done Flash SlimKat Stable and Gapps. Reboot without Kernel flash.

Rom will want to go through the setup including installation of your Apps from Play store. DO NOT restore any backups. Once that is completely done, reboot once more, just to make sure the phone boots in reasonable time. After that go back to recovery and flash Kernel 7-1 for ATT only!!!! Wipe Dalvik and Cache again!!

The New Rom option does Factory Reset so you don't have to. I don't think you need to do Odin. But if you want to fix TWRP's problems, you must do so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Alright that's all clear now with procedure. I used twrp for 2 years so I got use to it. Philz things are in different places and or missing or called something else.

I'll be attempting all this in a few hours when I get home.

Fixing twrp might be as simple as factory reset? Then installing twrp.

I known this isn't the place to talk twrp. I'll just stop now lol going to post in twrp thread see if I get some light.

Cheers I'll report back tonight.

Edit. There is no possible way I could download the wrong device kernel when I download from this thread only is there? Besides aosp or tw obviously lol. Had me curious why u had in red for ATT only!!!! I pretty much can't muck that one up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
If want the latest twrp, install ROM installer from the market. It has the option to install the latest recovery. Goomanager it's not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
If it was only that easy man... For me. I can install no problem just all the mounts are 0mb. Therefore twrp is useless for me. That's why I'm on philz touch for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You never know. Stranger things have happened. The Kernel zip file would contain the carrier abbreviation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deathblade:
Try reformatting the filesystem to ext 4 I've had to do that a few times fixes a lot of issues I believe it can be done in recovery not sure if Phil's cwm has it but I'm pretty sure twrp does make also fix your issue with twrp (please note it will erase everything on your internal storage so save anything of importance to external source)

---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------

Steps to format with twrp is

1 backup important files

2 reboot recovery

3 go to wipe

4 format data and select ext 4

And start

Then proceed to proforma a clean wipe of ROM and gapps

Reboot without flashing kernel

Go trough the setup process

Reboot

Reboot recovery

Wipe cache and dalvic cache

Flash kernel

Reboot

( I personally find wiping before to be more effective in preventing issues)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Phillz lets you do this. It's in the advanced settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Hey man. I've just been busy haven't had enough downtime to try what Perseus instructed me to do.

I will report back once I get time. Hopefully by the weekend.

Thanks again for all your help. I will report back asap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brayhanrd:
what the experience whit CM11 ?

HAVE SOME ONE USED IT WHIT CM11 M9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
I full wiped
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
I've tried the JB kernels a few different times and following instructions. Each time I could watch my battery life dropping. Do I need to reflash the cm10 rom then the kernel or can I just flash the kernel, wipe, etc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Just flash the kernel AFTER the ROM is in there. CM10 is very experimental, dont expect anything out of battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
Well what I meant was that before I flashed the kernel I was getting great battery life. I'll try it out again tomorrow though, thanks for answering!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Might to let the battery settle in, I usually start seeing great battery life in 3-4 days
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
I'm on 19c Sammy. While streaming Bluetooth to my Volvo I get a staticky sound. Same for gps navigation voice. Only thing that seems to stop it completely is to put the governor on performance. Any other setting it keeps happening. Tried scheduler settings too. Any idea? Tried upping volts slightly on low freq and didn't help either.

Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Roco91:
7/22 Jelly is running great, everything feels smooth. Love having 192mhz again, and maybe it's a placebo but it feels like battery is better. Great work man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Running diet ics rom. The sammy kernel is working great :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omar300:
Works on CM10! :D

Thank you! made my cm10 even faster.

I had amazing battery on cm10, after installing this and underclocking to 918mhz i will see how much more can i keep the phone alive.

btw even at 918mhz phone feels just as fast at 1890.

pretty cool work you have done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cwburns32:
I have same issue and it's not just with bluetooth but any time you play any audio out of the speakers, bluetooth or headphones you get that staticky sound. KT told me that it was my ROM but I knew that wasn't the case because I knew people who I work with with the same ROM and Kernel combo and no issues. So he suggested a full wipe; I flashed stock rooted through ODIN, reinstalled rom and reinstalled kernel and no change, same issue. I even uped the voltage values 100 on each step but still same problem. I'm hoping next update will resolve this issue but it seems KT is leaning towards the AOKP and JB side of things with this kernel which is fine because I fully intend to flash CM10 once it becomes more stable.

My question to you KT is if I were to flash Faux's kernel over this will WiFi and BT be broken? If so how can I get old drivers back?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I dont know anything about his kernel. If he did it right, he should be flashing the drivers during kernel flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Ktoonez which govenor do you recommend for best performance/battery life. I see in the change logs that you tweaked both, but then in the newer AOSP version you started from scratch...I got great battery life with ondemand/cfg doing a overnight idle drain test lost about .25% an hour.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
I was using Power AMP this morning to listen to some tunes while ironing a shirt and I had some weird audio artifacts as well. Not so much static, it was more of a techno-ish blipping. going on. It did not seem to do it on lower quality files. These files are located on a 32GB external SD Card, if that matters.

Also, I am on Diet ICS ROM, if that matters.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Still on ondemand and cfq. Always been my favorite :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
Thot your favorite was Ondemand/Noop?? :confused: :laugh: