yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
I saw the mediafire link but it's apparently down. Can you please upload it again? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
My bad KT. I just didn't give the kernel enough time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
So far working smooth down to 96mhz at 770mv on Slimbean Aosp with deadline / interactive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
384 when I'm playing music and 96 for the rest of the time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
So the black screen issue only happened to me twice all day, which is much less than it had been happening. Just a heads up. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for all the feedback guys:D. I am seeing the same thing all of you are. It is most definetely better but still there once in a while
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
My bad for post this in this thread but I would like to try this out rom out http://xdaforums.com/showthread.php?t=1732191 but I have KT tw/jb rom and in that rom i linked they said to use kts kernel but which one though lol.. I mean I flashed the tw/jb version after flashing the rom and it just kept looping samsung logo and it kept vibrating so Idk which kernel to flash..thanks for the info.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
That's TW alright. IDK why it won't work either as I don't go near TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
thanks for the reply I would like to try it..but not sure which kernel to use.. idk but im not sure what roms support the nfc feature about file transfering to other phones because I have been using that feature a lot cause friends and some co workers has the s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
TEST #2

TEST #2:

Here is a test kernel for those that are getting the issue on AOSP where the screen doesn't want to turn on after it is sleeping. Report back what you see.

http://goo.gl/kqjyZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sfernandez:
Im still getting it...I can shut off screen then turn on then off repeatedly ..on every 5-8xth time it will act up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
Ditto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Wipe cache/dalvik and fix perms
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
Yeah
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Guess Ill have to wait longer, Im going on over an hour and about 300 on/offs still not one black screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
Ok, So I had it a few times after I flashed the Kernel, but I havn't had it for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sfernandez:
+1 on that..I always do

Sorry couldnt help you more

Edit: just tried to duplicate problem and 30xs so far and all is good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
But seriously, hope this is resolved quickly. Love your work.

AT&T SGS3 Marble White

ParanoidKangDroid 1.4 ROM

KT747 11/13 kernel OC'ed & UV'ed

Medical Marijuana Supporter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
Yeup. I can no longer reproduce the issue. I'll give it some more time and report back tomorrow.

I also had an issue when on a call. If I would pull the phone away from my face the screen wouldn't turn on all the time. That also seems to be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I would think that the issue could definetly be reproduced within 50 cycles..for me I know it could..out of at least 100 cycles I had one black screen on the first test kernel ..flashing second now

-Nexus7-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That was my big problem too, it did it almost 100% of the time when the other person hung up before i could, then I would be stuck in the call and was very hard to get the screen back on. I have had 7 calls and not one black screen yet. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
I called my self from Google Phone 5 times and tried a few different things to try and mess it up and it worked perfectly! So far everything is working great. Now if someone could fix the my no audio in recordings I would have a 100% functional Rom!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sfernandez:
All is good on my calls now also:D..i reflashed and cant reproduce screen not waking up with screen off..so fingers crossed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
just did another 50 cycles on test 2 kernel..no black screen so far :)

-AT&T SGS3-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Got one black screen after reboot. Now, all is well. :) Awesome, boss.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Thanks for the update ktoonsez! It's sleep time for me but I'll be sure to see whether I get black screens tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I OC'ed to 2.1GHz successfully and stress tested to make sure it's stable. However, the phone lowers the max frequency(typically between 700 and 1200MHz) on its own. Is this thermal protection or some sort of error?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey guys sorry for jumping in late, i've been AFK for a few days, that can seem like a lifetime on xda though.

I've been getting the occasional black screens, it always comes up after about three button tests. I thought for awhile it was the slightly unstable PAKang 1.2 rom i was running(soon to be 1.4), now i'm not so sure.

Lets weed it out seeing if it's the settings. :laugh:

What are you guys doing for screen off frequencies/min frequencies?

I'm at minimum of 144, screen off max of 384.

what about other random settings like custom vibration numbers? mine is 90.

also i'm under volted, by a lot. but that shouldn't do it.

i don't have a screen off governor.

no touches on the governor tweaks, no messing with the touch boosters.

INtellidemand and cfq for regular gov.

---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------

I have dealt with a hot chip when stress testing, not fun...

when i did stress testing at super high OC i would toss it in the freezer for a few minutes. that would rule out the thermal regulator kicking in. i would get lower benchmarks when over clocked than when i was at stock frequencies.

if i remember right it would turn off a core when it got hot, could be wrong though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Either it is thermal prot kicking in or u didnt "Lock Frequencies".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
how do I download older versions like tw/jb 10/31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Happy thanksgiving ktoonz

"Lead me, follow me, or get out of my way. "
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Thanks for the work here and in AOKP thread, sir.

Happy Thanksgiving to those in the US or abroad that are celebrating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
No freaking way...

So insurance sent me a new phone (garnet red SGS3) to replace my white SGS3 with cracked glass. I decided to give this kernel a try because I know Ktoonsez has mad skill. Now keep in mind, it would not work at all on my white SGS3. It is working, as of now, perfectly :D

So in summary, white phones don't like ktoonsez haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
I killed my battery last night and when I turned my phone on this morning I had one black screen. But since then its been fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
EXCELLENT MAN!!!!!! :highfive: :good:. Glad to hear it.

Happy thanksgiving everyone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamandor:
Hey guys, I have been reading the last ten pages or so, and I searched the thread. Just wondered what the consensus is on the best settings for optimal battery life? I know this is a very subjective question, and depends on all sorts of variables.

Right now I'm lucky if I can 3 hours screen time on a full charge, with normal use, average brightness etc.

I'm just looking at governor/scheduler, cpu min/max and voltage settings. Appreciate the insight. :)

BTW, I'm running the latest version of task's AOSP rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z34370z:
My white phone works fine on ktoonsez kernel :/ lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No one can really answer this for you. All you need to do is just play around with the settings to find the sweet spot for your particular device. 3 hours of on-screen time is pretty good dude. not sure what the problem is. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] exodus454:
I've been wondering the same thing. I've played with all sorts of governors, under/overclocking, screen brightness and timeouts, installed juicedefender, etc and the best I can usually do is about 3hrs screen on. I also have my governor set so the 2nd core only gets used under the heaviest of loads, and I'm usually on wifi with a good cell signal. I'm running the same ROM too. I haven't really been able to improve battery life much, despite lots of trying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nickovtyme:
I've been playing around with this kernel and my prefs don't seem to want to load at boot. I have to go in and ktweaker says they don't match.

I've V6 Supercharger running and wonder if that may be a cause of it. Could it be conflicting in some way?

Do you recommend/advise not using V6 or does it matter one way or another?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamandor:
Good stuff, thanks. Not having a problem really, but I've seen others get 4 or 5 hours, but that's probably because they're only on Wi-Fi and have brightness at zero. I'm not willing to live in the dark ages for an extra hour of battery life lol

Cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It could be the V6 or just the ROM. Have you played with the time delay? Usually 5 seconds works for most or even 10. But the opposite has applied for some too, going to 1 second or immediate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Happy Thanksgiving ktoonez! Thanks for this extremely awesome kernel :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You too man, have a great day!!!!!!! :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nickovtyme:
Yes sir..have tried them. Currently am running just a rooted nearly stock ROM that I V6'd and added unit.d support to. Was wonder if I could use setcpu? I tried setting it up but it doesn't read the OC values..just the defaults.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
U can use SetCPU if you don't want to OC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
This version works perfectly... For now.

I used to have black screens all the time and since i installed this, not even once!!

Thanks for your amazing work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
For my black screen issue, I have been running intellidemand and deadline, which seems to help minimize it. I don't have any other tweaks. Using KT's test 2 kernel, but still getting the back screen sometimes. Had the same experience with the Test 1 kernel. Both the underwear kernel with task's ROM and KT's 11/13 kernel had the black screen occurring more frequently though. Using task's 11/18 ROM.

FWIW, the last time I did not have black screen issues was the combo of task's 11/04 ROM and KT's 10/31 kernel.

Sent from my SGS III. Give credit where credit is due...and hit the THANKS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nickovtyme:
Right on...I can do that...but it takes the OC fun out of it. :D

I'll keep messing with it, I just know I'm missing something simple that's causing the prefs from loading on boot...maybe its time I put another ROM on here.

Thanks for your time and work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The black screen issue has been in there since about 10/14, havent been able to pinpoint the exact date. We will be getting the patches into the stock AOKP kernel so the black screen should be minimized drastically with that kernel too.

P.S. I havent had the black screen in about 20 hours now with 11 calls and about 1000 quick on/off screen tests, cant believe people are still getting it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You could also try a factory reset/full wipe and fix permissions and see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
HERE IS TEST #2 AGAIN FOR ALL THAT MISSED THE POST:

Here is a test kernel for those that are getting the issue on AOSP where the screen doesn't want to turn on after it is sleeping. Report back what you see.

http://goo.gl/kqjyZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
OK. When I get a message from a program, it will cause the screen to need a triple tap on power to pull up. Text, Facebook, POF and okcupid . Not email or tweet notifications. Not every time but that's the only time I see it.

Aokp 11.18

Test 2 96-2106

Intellidemand/deadline

Default voltages

Vibe at 80

Screen off max 384

Brightness all the way down
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Try changing screen off to 486. 384 is too low
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skatin707:
Yeah, I'm stoked to be back on your team again! Thanks for your work buddy, happy thanksgiving :D

No matter what I tried, I couldn't get it to work on my first S3. Broke the screen, insurance swapped it, the kernel works on this one :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Nice. The 2nd test kernel fixed the black screen for me. My screen turns on the first try. Nice work ktoonsez :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
384 runs fine. No huge difference between either clock speed though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] picklerick:
Is anyone having issues with Bluetooth devices disconnecting with the aosp jb version? My devices randomly disconnect but I'm not really sure if the kernel, cm 10, or one my settings is too blame.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I locked frequencies. It's working fine today. I played some games and took some photos/photospheres with the 4.2 camera in the sun and it didn't throttle. Anyway, thanks for the awesome kernel and happy Thanksgiving!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
I just noticed something very weird. My cpu seems to only run at my max frequency (1512), even after reboot, governor change, voltage change, everything. Anybody have the same problem?

Edit: restored nandroid without the kernel, now it works fine. Gonna try the kernel again tomorrow
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Had the same problem. It was weird. I just reflashed 11/13 but I think its still happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ATS2:
I haven't had any issues since flashing it. So far so good. Many thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Should I flash this anyway even if I'm not getting the black screens.... you know the saying about if it ain't broke, don't fix it. Is this a fix in that there is something in here better than what I am running in the 11/13 version?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
O

You'll probably be alright flashing it but if you don't have the black screen issue I would wait for the next official release

Edit: unless you want NTFS support, which I think is included in this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Coblica427:
Just an update on my screen wake issue

I'm currently using the smartassv2 governor and cfq io scheduler. I also up'd the minimum frequency to 486. I haven't had a single problem getting the screen to wake back up. I'm more convinced it was the minimum frequency bump as opposed to the governor however. Something y'all can try...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Awesome, we love hearing about it in two threads
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Im running kt747 10-13 kernel without a single black screen. Screen off freq on 384 and -100 across the board. Ktoonservative/sio. 384/1.6 min/max. And this version gives me the absolute best batt life. 6 and a half hours screen on with an extended battery for both me and my wifes s3. Wifeys s3 has exact same config as me. Ive tried all of kts versions from 10-13 thru 11-13. Maybe you guys can try an earlier version too see if maybe its the latest release?

SGS3 JB 4.1.2 Ktuned Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
http://xdaforums.com/showthread.php?t=1934611

Im trying to use frosty jb and it says tonuse kt kernel I had tw jb kernel on here but when I flash it phone wont load what kernel should I use then
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
You should search the thread - this has been covered - a lot. So much that I'm not even going to post a link for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] busarov:
+1

Bumping my screen off freq from 384 to 486 and updating to the test kernel fixed my black screen issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Coblica427:
Well I just got my first black screen since upping the minimum frequency. I had changed the io scheduler to noop and after receiving an SMS the screen didn't come back on. I changed the scheduler back to cfq to see if it happens again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
Sooooo with the latest test kernel. Not a single black screen issue here. Not. A. Single. One. Yayyyyyy

Sent from my Samsung Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nst6563:
do a search on the thread for 10.31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
I posted links a few days ago
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
Got a black screen on test kernel after getting a text message cpu was running over 1ghz bc i was on bluetooth with a min set up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
so I tryed this and searched on the rom that Im using and i flashed the touchjizm on the frosty jb just sits at android logo..beacuse I need one dated for 10.31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
The link noted above is the ICS TouchWiz version and not the JB version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
O ****, your right, sorry guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noamaniac:
My blackscreen issues were fixed by turning off circle lock on tasks rom and going back to slide. I realized that any blackscreens i was getting started when that lockscreen became available. sio/interactive 96/1512, -100 across the board. no blackscreens and no soft reboots when i attack the power button to force screen on/off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yamahakid:
i flashed this last night on DG's 747 M7 rom, and it was running great. when i just woke up this morning my phone was sitting on the samsung boot screen and now refuses to go past that. any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Garrytheogre:
Have you tried pulling the battery and seeing if it boots?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yamahakid:
Yes I tried that, as well as clearing cache and dalvik. I even tried re flashing the kernel but that didn't work either. I just ended up restoring a nandroid with the stock kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
from what I read, every once in a while when this happens its from flashing a touchwiz kernel to an aosp Rom or vice versa

-AT&T SGS3-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yamahakid:
I know I downloaded the correct version, maybe just a bad download or something. I'll download again and give it another try
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdidtht:
The wrong kernel would just be a complete no boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
edit..start with re-downloading..double check its the correct version..make sure your ROM is updated to something new whether it'd be cm or aokp..also make sure your recovery is up to date..try flashing the kernel after a fresh and clean ROM flash..be sure to wipe everything..easiest way is to start fresh

edit2- just re read and seen you said it successfully booted once so I would be wrong about it being the correct version for your ROM..

-AT&T SGS3-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hiquin:
Just thought I'd throw a little post up here saying that this kernel 11/13 works great with Paranoid Kangdroid on my Telus S3.

I had stock rooted my phone, and put on the TW 11/13 kernel(as well as many previous versions of the TW kernel), and everything was great. But, as I do with my phones, I wanted to tinker more. So I decided to go the route of flashing Paranoid Kangdroid.

I wiped, flashed PK, wiped again, flashed the JB version of the 11/13 kernel, wiped again, fixed permissions, and voila, everything is great!

The only hangup was that I needed a specific version of Clockwork Recovery for PK to flash onto my telus phone. I had to put on 6.0.1.2 NON-touch version. If I tried the touch version, or 6.0.1.5 of the non-touch, I got a build prop assert error on d2att. 6.0.1.2 was the only one that worked.

Anyway, this kernel, combined with that rom, has increased my battery life even FURTHER. ktoonservative/noop, 384-1.5 -50 undervolt on 384 - 594
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Same Rom, same kernel. i am running the latest cmw touch. no issues at all. maybe you made a mistake typing in the terminal commands.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Decided to try AOSP test kernel #2 and it's been perfect so far (only about 3 hours).

Only problem I've noticed is that it didn't install KTweaker. Is it not included, or did I do something wrong?

Perhaps you assumed people would be upgrading from 11/13 which includes KTweaker. Personally, I'm coming from Task's stock 11/18 kernel.

Not a problem - I'll just use Voltage Control.

Thanks for the killer work! :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I stopped using ktweaker. Noticed I had better results with setcpu

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
How so? What is better?

== Yea.. I tapped that!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its not included.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
What's the link for test kernels again?

Sent from my Samsung Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
just check back within the past two or three pages bro..you will see them..I believe test two KT posted twice

-Nexus 7-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Thanks for the response. I figured as much.

Just got two black screens in a row. Black screen followed by a proper wakeup followed by a black screen.

Oh, well. This bug seems difficult to squish.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It is still there, but 10 times less frequent that is for sure, I went 3 days without 1 and then had 5 today when the phone got really hot from being out in the sun for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Actually you should remove setcpu and any other application that can modify CPU settings and use KTweaker instead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
I agree. KTweaker is great.