yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] galaxys3man30:
Hey bud run the kernel cleaner before you flash this kernel the kernel cleaner is in the op try that next time
[Sprint Samsung Galaxy S III] haoleflip:
I do that every time. I just tried to use CWM touch and flashed TPR, but still having boot issues. I'm telling you, my specific phone doesn't like the kernel for some odd reason.
[Sprint Samsung Galaxy S III] PaulB007:
trust me, I feel your pain because I had the same issue on my old galaxy s 2!
[Sprint Samsung Galaxy S III] haoleflip:
Yeah, I actually went with agat's kernel and its great so far. Wish I could have used this one though...

>>The People's ROM GS3.0 JB 4.1.1 w/Agat's custom kernel v0.3.2 @1.89ghz
[Sprint Samsung Galaxy S III] JAG50:
I tried Agat as well, but after waiting three days for kernel to settle, and never saw the battery savings I was getting with KTZ. If was nice to be able to load custom boot animations, but the main goal for flashing kernel is to gain battery power.
[Sprint Samsung Galaxy S III] bsanto9:
hey ktoon do you think you will be adding RGB setings or sliders? in the future
[Sprint Samsung Galaxy S III] Ramondel:
Did you try using Agat ktoonservative governor and tweaking it just like kt747 kernel?

Ramon
[Sprint Samsung Galaxy S III] ktoonsez:
Maybe down the road, I have tried a few times and never found an easy way for the user to interact with it since the newest technology all utilizes mDNIe tables to accomplish color/gamma.
[Sprint Samsung Galaxy S III] mw86:
Speaking of those is it always best to leave that set to UI?

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] ksmullins88:
is anyone experiencing the volume skip mod break when flashing this kernel?
[Sprint Samsung Galaxy S III] joelespinoza:
Hey I had a question for Ktoonsez, do you know if the voltages in KTweaker are actually correct all the way down to 700mV? It appears that the processor has no difficulty running on very low voltage as long as it doesnt have to switch frequencies. IE I have my phone min/max frequency both set to 1998mHz and the voltage set to 700mV and it seems perfectly stable. However if I unlock the min frequency it immediately crashes, so I just leave it at the max clock and it seems fine.

Kernal: Ktoonsez 3.0.51-kt747-gd1f1083

Rom: Frankenstein's kilJoy7 v2.1
[Sprint Samsung Galaxy S III] nicholaaaas:
ktoonsez,

CM10.1 just saying. Sure you're already on it
[Sprint Samsung Galaxy S III] mw86:
I posted in the other thread on this and i don't know anyone believed me or cared. I see the same thing repeatable 100% of the time. So it seems its when it switches from one frequency to another and then therefore applies a different volt. In my opinion when first applying the volt like that i don't think it applies till tge cpu switches to that frequency through scaling so i believe the original volt is being used until it scales and moves to that voltage in the voltage table. To me this explanation makes the most sense. I can also do just what you said. Though testing with scaling shows truly where volt handling of a frequency is. Thats why for example Ktoonsez phone actually shows its unstable on a huge undervolt. Its true that when set like normal these cpus are vulnerable to too low voltage just like every cpu ever made. Juat my humble opinion. You might find the max cpu frequency never is capable of it just the next one down which leads me to believe when the frequency above it is not undervolted it keeps this happening but put all to 700mv and min max the same as long as its not max cpu frequency set it stays stable on 700mv.

I tested cpu temp before and after. There is only a slught drop in temps indicating ita not using 700mv because if i properly undervolt that frequency (and allow scaling) i don't reach as high temps on that target frequency.

Id prove it but still haven't thought of a way that won't be falable to argument.

The voltage is applied and correct in voltage table at the time as you can use terminal to check. The issue is they don't get used till the cpu moves atleast one up or down. It uses that volt once cpu changed to that frequency and not immediately when applied. This explains why the voltage table can read 700mv and all is stable till scaling is renabled.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] ktoonsez:
Nothing on the download server, CM10.1 is still waaaaay in flux.
[Sprint Samsung Galaxy S III] awillis111:
THIS!!!
[Sprint Samsung Galaxy S III] ktoonsez:
OP Updated

AOSP JELLYBEAN: Download CWM flashable zip kernel

http://www.mediafire.com/?0pt3ssvyz74j87d

Touchwiz JELLYBEAN: Download CWM flashable zip kernel

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

Change Log 12.11

1. Linux 3.0.52

2. Linux 3.0.53

3. Linux 3.0.54

4. Linux 3.0.55

5. Linux 3.0.56

6. Tweaks to lulzactive

7. Quite down the vibration driver which speeds up typing and capacitive buttons

8. Changes to Bluetooth Mhz setting logic (its nearly perfect now, only issue where it might revert is ending a call)

9. More TCP filter code from madmack

10. Merged in TMO and ATT official TW-JB code

11. Black screen code from the test kernel is in here to reduce black screen wake issue

12. Thats all I can think of and ENJOY!.... :good:
[Sprint Samsung Galaxy S III] cballin22:
Since installing latest build I'm getting screen flickering randomly when min sent to 192 if I got to one step up its fine n I'm at stock voltages...... Actually checking disable hw overlays corrects the issue
[Sprint Samsung Galaxy S III] akarol:
Not a biggie, but I cannot get my FreeGS3 default boot animation to work. It goes to black after Samsung logo. Not a biggie, but I'm confused. The bootanimation.zip file is still in its original location (/system/media) and I also tried copying it to the (/data/local/) folder to no avail.

Aside from this, I can easily confirm that this is the best Kernel out there hands down! Good work!
[Sprint Samsung Galaxy S III] ktoonsez:
Thanks man, if you are on a TJ ROM and not AOSP, you have to do some extra stuff since I dont run AOSP bootanimations on the TJ version of the kernel. I think its as easy as renaming the file to a different extension (.qmg I think). You'll have to search around. :good:
[Sprint Samsung Galaxy S III] Ramondel:
Akarol, I had this issue but fixed it by flashing CWM_CustomBootanimation_Enable.zip, do a search on it. KennyGlass123 has posted this in various threads and I have as well just forget where. I will need to just copy it and have it handier.

Ramon
[Sprint Samsung Galaxy S III] ktoonsez:
Once one of you find it, post it up and Ill put it in Post #3.
[Sprint Samsung Galaxy S III] clothednblack:
@ ktoonsez I sent you a pm

Ridin the Mystic jellybean unicorn on my Ktweaked SG3
[Sprint Samsung Galaxy S III] ktoonsez:
Yes I did get it, havent had time to build another one again. Ill try right now

EDIT:

Here it is:

http://www.mediafire.com/?rmya0f4l1yusu3a
[Sprint Samsung Galaxy S III] Ramondel:
Ktoonsez,

Here is the link it was posted by anbech:

http://xdaforums.com/showpost.php?p=31833122&postcount=4

Ramon :eek:
[Sprint Samsung Galaxy S III] mw86:
Hey Ktoonsez loaded everything up. Im on PACman rom AOSP and running solid. Thanks for the update. Btw everyone especially me loves Ktoonservative. Top notch KT.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] ktoonsez:
Thanks for the link, it is now added to Post #3 :good: :highfive:
[Sprint Samsung Galaxy S III] ktoonsez:
Thanks man, awesome to hear :highfive:
[Sprint Samsung Galaxy S III] akarol:
The Boot Animation zip worked flawlessly! Thanks.

However, I must say that the latest version of the kernel is a bit more sensitive than the last. I was able to underclock 100mV across all states on your last kernel while this one will gives me consistent reboots at that level. So far - 75mV seems stable.

Does this new version give any speed or battery improvements over your last? If not I'm thinking of switching back. What do you think?

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] awillis111:
I'm hoping I got a bad download of the latest build. After flashing, the display had 90° and 270° reversed.
[Sprint Samsung Galaxy S III] ktoonsez:
I would stay on this one since it has all the official updated code from Sammy for the ATT and TMO versions that we all benefit from, plus if you do a lot of typing, the Sammy debug code I removed made typing much faster.
[Sprint Samsung Galaxy S III] akarol:
Interesting. I'll stick with this one for the time being then.

By the way, I'm on noop with ktoonservative with default max and low of 384 with - 75mV on all states. What setup do you recommend the most for good battery life without sacrificing too much on performance?

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] EeZeEpEe:
Glad to see you're still active and updating. Thanks!
[Sprint Samsung Galaxy S III] galaxys3man30:
Anybody that on a tw rom come to my to my thread for tips and tricks and tweaks for awesome battery life and other things and aosp roms there tweaks for y'all as well all tweaks r for the ktoonsnative governor and thanks to ktoonzs for the great kernel

http://xdaforums.com/showthread.php?p=35101228
[Sprint Samsung Galaxy S III] ktoonsez:
See post before this one and try adding a screen off mhz setting of 486 Mhz and see how that goes.
[Sprint Samsung Galaxy S III] galaxys3man30:
Ktoonzs come check it out I want your opinion on the thread too buddy after all it is ur kernel
[Sprint Samsung Galaxy S III] ktoonsez:
Will do, working on mr1 right now though, Ill come check it out tomorrow :D :good: :highfive:
[Sprint Samsung Galaxy S III] Logix:
Your the best thanks for maintaining us
[Sprint Samsung Galaxy S III] Pithism:
This new kernel AOSP 12-11-12 edition wont work with CM 10.1 will it? Just 4.1.x builds
[Sprint Samsung Galaxy S III] ktoonsez:
4.1 only
[Sprint Samsung Galaxy S III] awillis111:
Bout to bust this out on PACman.
[Sprint Samsung Galaxy S III] JCJ77:
Cballin - I was noticing the same flickering on my phone after flashing this kernel. I don't remember the setting under ktweaker (I've since re-flashed the pacman ROM to return to "stock" kernel) but under performance, I am currently at 384 (min) and 1512 (max). So, you are saying that checking "disable HW overlays" under development options works to get rid of the flickering? What settings are you using? I had my ktweaker settings at what galaxyman and mw86 recommended in a previous thread. Thanks, brother.

Sent via Tapatalk from my SGSIII running the hottest ROM right now! ;)
[Sprint Samsung Galaxy S III] drose1976:
I was experiencing the same flicker. Mine was occurring with default settings on the Wheatley governor and ktoonservative and deadline i/o.

I didn't think about disabling hw overlays.

I will have to try that.

Sent from my PAC-Man SGSIII. Yeah, he's moshing on a power pellet.
[Sprint Samsung Galaxy S III] JCJ77:
Cool. Let us know if it worked for you.

Sent via Tapatalk from my SGSIII running the hottest ROM right now! ;)
[Sprint Samsung Galaxy S III] drose1976:
So far so good. I haven't done any tweaks this time. I am going to let the default settings settle in a bit. But disabling HW overlays has worked.

Sent from my PAC-Man SGSIII. Yeah, he's moshing on a power pellet.
[Sprint Samsung Galaxy S III] JCJ77:
Nice. Thanks for the feedback. So, regarding letting the default settings settle a bit...is that good practice? I ask because when I have flashed a new kernel in the past, I immediately changed the settings. If its better to let the default settings settle a bit, I will start doing that.
[Sprint Samsung Galaxy S III] awillis111:
I see in Ktweaker>Extra Settings that there is an option for sweep2wake. Does that actually work. And if so, where do we swype?
[Sprint Samsung Galaxy S III] ktoonsez:
Usually only best to do it while plugged in since it needs to maintain a wake_lock. You sweep from far left to far right. :good:
[Sprint Samsung Galaxy S III] awillis111:
Ok. Kinda hard with a OB Defender and far fingers anyways.
[Sprint Samsung Galaxy S III] DC_MTP:
been trying everything possible to get this kernel to play nice with my phone. I'm also suffering from the flickering effect / menus going black then coming back when clicked effect. I just tried "disable HW overlays" - no dice. also tried the kernel cleaner. never messed with the ktweaker app.

on Phantom Hacker 2.1 jellybean...Yes I'm installing the touchwiz version of the kernel.
[Sprint Samsung Galaxy S III] galaxys3man30:
Is it Android 1.1 or 2.1?
[Sprint Samsung Galaxy S III] DC_MTP:
4.1.1
[Sprint Samsung Galaxy S III] galaxys3man30:
The kernel may not just agree with ur phone buddy I can't figure it out what's going wrong
[Sprint Samsung Galaxy S III] DC_MTP:
I find it strange that I've also tried Agat kernel and notice the same effects. But when on stock kernel all is good.FML
[Sprint Samsung Galaxy S III] EndlessDissent:
Yes, any AOSP JB ROM.
[Sprint Samsung Galaxy S III] ktoonsez:
LMAO, wait a second, I see now. There is no sammy kernel for Sprint, thats your problem. You cant use my ATT kernel, the gyro's are different and thats why you are having issues.
[Sprint Samsung Galaxy S III] ktoonsez:
I am not seeing that, I am on task's and I AOKP ROM of course. I cleared stats in CPUSpy and ran Quadrant and saw it hit 7 different frequencies. Easy fix is to try fix permissions. Hard fix is to fully wipe.
[Sprint Samsung Galaxy S III] EndlessDissent:
I did a full wipe to begin with. I'll try fix permissions and let you know. I know someone else reported the problem with the CM kernel, so I'm not completely crazy.
[Sprint Samsung Galaxy S III] nicholaaaas:
msm does scale above 702. i just watched it
[Sprint Samsung Galaxy S III] EndlessDissent:
What were you doing? I ran quadrant, and it did scale above 702, but unless I'm running quadrant, it doesn't scale over 702MHz like it should. It's like the load has to be over 2000% for it to scale any higher than that. I just played through a mission in GTA3. Out of 6 minutes of play time, the frequency was at 702MHz for 5 and a half. The game was barely playable.

Edit: This is after playing the same mission in the stock ROM. Obviously, something is not scaling right in the AOSP kernel.
[Sprint Samsung Galaxy S III] clipsruck:
I'm having the same issue still. It's happening on EVERY rom and EVERY governor.

I've done everything I can think of.

Full wipe a few times.

Different apps to control the values.

Freeza's dual core fix.

Blah blah blah...

I was looking through the init.d.post.boot (whatever that says) and wasn't sure what the correct one should look like. I'm going to pull one from a stock rom and take a look. I'm coming from an evo 3d and the settings aren't what I remember and I'm no dev or anything so I really wouldn't know too much anyway.

But, no matter what, I can't get the cpu values to stay where I put them.

Maybe it's the lg8 firmware...
[Sprint Samsung Galaxy S III] nicholaaaas:
What you described as your problem and the previous problem described are two different things. If your settings are not sticking make sure you checked set on boot. Otherwise I'm not seeing anything out about of the ordinary with the pegasusq or the msm gov. I know noobl said there are new things nlthat need on demand or interactive to utilize so give them a shot
[Sprint Samsung Galaxy S III] clipsruck:
That's the thing. I am aware of all that. And by sticking, I don't mean upon reboot. I mean a couple of seconds if not immediately after I change them. It goes back to 702. If I change to msm it defaults back to 918. I did extensive searching and reading. I'm wondering if maybe I picked up a bad script somewhere and cwm is not fully wiping system files. I am going to flash twrp and see what happens. I'll report back.
[Sprint Samsung Galaxy S III] mw86:
Ktoonsez nice job on updating all those lines of code. I ran the latest Paranoid Android stock kernel since it was posted. Its been 100% stable no reboots. I checked phone after charing over night and it never shut off on me both nights. which when I was having issues everytime I'd check my phone in the morning I could see it rebooted. Now i'll load up your kernel again ;) I have a feeling it will be 100% better since the reboots I had must of been from the roms and seemingly thats been fixed. can't wait to get back the overclock undervolt. I'll use it awhile like I did PA stock kernel and report back. I have a feeling I'll be able to undervolt now and not wonder was it volts or a random reboot... Cheers thanks Ktoonsez. FreeCharlesManson I should have no prob on the governors now. I plan to stick to the rom and kernel as is without tweaks. No Freeza, no Eugene fix, no Dual core always on. I use System Tuner and the option fast app loading though, im guessing that on is no prob. I plan to try the Pegasusq governor and Sio since its available but when its not in a kernel I prefer Noop. I'll also retry Conservative governor because I want to save power sometimes but have power at hand if and when its needed...

MSM i used past 2days on stock latest PA rom and it ran fine but I do notice it never showed me 1500mhz but I don't know when its supposed to. I used Cool Tools app from the market free and I set it to look like Jelly Bean Status Bar. It can hide in full screen apps like the status bar which would be good if you use it all the time and not hide if you prefer to see the stats even in full screen 3d apps... but that would be for monitoring purpose only. I use it to show cpu usage and frequency and even per core usage in a bar graph, network data rate.and much more but I mainly just use those. Can update in seconds of 0.5, 1, 2, 5,10. Anyways I notice my cpu ran similar to what was posted in cpu spy above. thats is not on your kernel but on stock rom Paranoid Android kernel. So my guess is whatever is happening has not a thing to do with your kernel as you stated Ktoonsez. I was on a clean wipe fresh install not a spec of data left behind as I always install that way and go through the tedium of restoring everything with Titanium Backup but without restore system apps or system data and lately for compatibility the apps without data too and I have to redownload anything that needs extra app data in the app but end result is i am untainted by old left behind ghost files :)

Going to load your kernel now... me I'll just avoid MSM since it didn't scale for me as well as any other governor in stock rom or your kernel. ON MSM is there a config file or anything that tells MSM what the highest frequency to use is?

Thanks ahead of time for any advice all you experts out there. Nice job Ktoonsez smooth buttery sailing from here.
[Sprint Samsung Galaxy S III] nicholaaaas:
youtube, quadrant. I checked it thru adb so I'm sure it's right. what scheduler are you using? im usung bfq
[Sprint Samsung Galaxy S III] EndlessDissent:
I went through every I/O scheduler except noop. They all scaled the same way.
[Sprint Samsung Galaxy S III] jamcar:
What is the best governor for battery life?
[Sprint Samsung Galaxy S III] IcOpRo:
I am currently using Ondemand and I'm getting pretty good batt life, I also have a profile setup to DC when the battery goes under 25% ... so far I have no complains.

10+hrs with close to 3hrs of screen time.

---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------

Oh and this is today so far after applying some UV which I believe it improved my batt life a bit.

With 1h45m of screen time.
[Sprint Samsung Galaxy S III] gyrra:
@endlessdissent

Just a wild shot in the dark....

Do you have powersave option turned on?

I know one option in powersave does so by limiting the CPU freq.
[Sprint Samsung Galaxy S III] EndlessDissent:
??? Powersave, depending on what you're talking about, is either a CPU governor (which I don't use) or a TouchWiz feature. So that's definitely not the problem.
[Sprint Samsung Galaxy S III] rkitect:
Is this a new kernel feature; pictures from the future?

This just happened after flashing from the stock kernel with the 8/12 cm10 ROM.

Still having screen flicker (is this what people are calling "screen tear"?) under this kernel so I think its either the device or the ROM.
[Sprint Samsung Galaxy S III] algirnavi451:
Its most likely ROM as I am on stock CM10 kernel and have screen tears as well.
[Sprint Samsung Galaxy S III] ktoonsez:
How you guys like that!!!! and 2.1Ghz
[Sprint Samsung Galaxy S III] ktoonsez:
It is the kernel (mine and CM's), CM is working thru the issues. It is all the new cool iommu and ion upgrades. Its gonna take some time but it will get there. The thing most people are talking about is a flicker when you change screens or exit an app. U really should be seen any tearing except on low quality avi/mp4's.
[Sprint Samsung Galaxy S III] drose1976:
I usually do if there has been any bumps. That way I can try to narrow down what I am doing to cause a problem. I have found over the last couple years that 99% of "bugs" are user error. Especially on kernels and Roms that have long track records of being solid.

I didn't initially report the flicker here because I assumed it was my own doing. I will start incremental tweaks over the next few hours and keep tweaking unless I Bork something. If I do, I will be able to report back here exactly what caused the Bork and what the exact settings were.

Sent from my PAC-Man SGSIII. Yeah, he's moshing on a power pellet.

---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------

Did you wipe cache and dalvik cache?

Sent from my PAC-Man SGSIII. Yeah, he's moshing on a power pellet.
[Sprint Samsung Galaxy S III] DC_MTP:
always wipe.. tried fresh install, re-download, ect. I think only other option I haven't tried was odin back to stock.
[Sprint Samsung Galaxy S III] galaxys3man30:
with this kernel to wipe cashes n fix permissions n flash the kernel n wipe ans fix permissions again before reboot
[Sprint Samsung Galaxy S III] DC_MTP:
will give it another shot per your instructions. brb.

Edit: no dice. thanks for your help galaxys3man30 and drose1976. Don't want to clog up the thread anymore. Will just stick with what works for me for now. will probably try to odin back to stock and start fresh later today. maybe some leftover mod or system file is causing this. others ppl have reported the same issues in other threads but the fix doesn't seem to be consistent.
[Sprint Samsung Galaxy S III] davidja92:
im on the latest update using pacman rom and mw86 55 65 tweaks and the charles i/o tweaks i feel like im getting blackscreen wake lock more did i do something wrong? i did wipe cache and dalvik and permission fix. other than that this kernel is the beez kneez
[Sprint Samsung Galaxy S III] algirnavi451:
I set a screen off profile of smartassV2 with a max of 756 MHz. So far no wake lock
[Sprint Samsung Galaxy S III] shinesthru:
Hey galaxys3man30, I appreciate all your positive attitude and willingness to help, but you HAVE to work on your spelling and punctuation, dude!
[Sprint Samsung Galaxy S III] galaxys3man30:
Lol thank you good sir and I will work that.
[Sprint Samsung Galaxy S III] mw86:
4.1.1 touchwiz jelly bean get touchwiz kernel

4.1.2 aosp jellybean get aosp kernel

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2

---------- Post added at 08:27 PM ---------- Previous post was at 08:20 PM ----------

I have seen it suggested that if its persisting raise your minimum mhz you can try 192mhz minimum. Assuming your using lower than that, that is.

PA AOKP CM10 Sprint GS3 JB AOSP Kernel Kt747 2.1Ghz BFQ/Ktoonservative >Tapatalk 2
[Sprint Samsung Galaxy S III] thznutz87:
Anthrax!
[Sprint Samsung Galaxy S III] JCJ77:
This is from ktoonsez kernel...no tweaking yet.

Sent via Tapatalk from my SGSIII running the hottest ROM right now! ;)
[Sprint Samsung Galaxy S III] thznutz87:
What it's it clocked at? Show the full score expanded please.

---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------

Lagfree causes black screen