yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Hey KT,

Excellent work on the test 2 kernel. Two days on it without a single black screen. Was getting it before about half the time, so HUGE improvement :good:

I saw a page or two back that KTweaker isn't included in that kernel? Is there a reason for it (I am guessing so)? Every other kernel you have released has had it to the best of my knowledge. If there isn't a reason, and in the future we need to get it on our own, how do we go about doing that?

Thanks again, and amazing work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I've used ktweaker for a while. But there's so many time where if my phone randomly reboots, any governor I put besides pegasus the frequency literally sticks to 1500 and I have no clue why. I would have to reflash the kernel and sometimes the rom itself to fix it. So I said screw it and disable ktweaker and tried setcpu. I have yet to have any random reboots and according to cpu spy the frequency are used evenly. And plus It might just be me but it feels a little bit faster and more stable. It could be just my phone...

After all I can't even use intelidemand. It sends it into a boot loop :(

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] killman2659:
I have a quick question about this black screen issue. I will be getting the S3 tomorrow and would like to run Ktoons kernel because i have used his Siyah and fluxxi from the S2. What exactly happens with the "black screen"? Does the phone freeze up and requires a reboot? Is it is serious issue? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r_scotter:
It's really not a big deal. Every once a while the screen doesn't come on when you hit the power button. Just have to hit it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
To be more specific, you occasionally need to hit the power button three times.

1 - Screen "on" (black)

2 - Screen off

3 - Screen on (normal)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I didnt include it cus the newest ktweaker isnt ready so you should use the one from 11/13 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Just to add on to r_scooter's response, this is a problem with many kernels and in the end probably isnt even gonna be a kernel fix. It is an issue only with AOSP ROMs so if you are a TJ user the problem doesnt exist:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jiggytom:
I'm getting an issue now with the black screen followed by a reboot. On the test kernel. Attached is my last_msg.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Don't know if this helps but I'm on the test kernel with task/ktoonsez aokp, slight uv, 486 min. I'm getting black screen when listening to music only. Home button does nothing when it occurs, must press power a few times. Anyways, awesome kernel doing awesome work with awesome battery besides that little thing which is probably aosp related anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
Same here happened once when listening to music, except I had to reboot with buttons. Running ktoonservative/deadline (with default KT settings)

Otherwise, I hardly ever get black screen when trying to wake. Keep up the great work, much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brorex:
The 2 selections on bottom are for schedule and scaling on set cpu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
Min - Max Settings

I have ROM Tool box that I use for a variety of things - and SET CPU which I use to adjust CPU stuff - when I first loaded Set CPU - the auto settings it gave me for Min and Max was 1026 to 1890 (Min-Max) so I adjusted to 341 Min and 1890 - then I ran Antutu and got horrible scores - much lower than I had on either stock or the previous custom kernel - for grins and giggles I opened Rom Tool box just to check the CPU settings and it said the minimum setting was 1026 -even though I had changed it in SET CPU to 341

Forgive me If I sound like a NOOB - but am I doing something wrong - am I reading this wrong or is something strange happening?

I just opened Set CPU and even though I had changed my settings to 341 minimum - it had the minimum settings back at 1016 again - see image
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxf250:
My experience is that I would not use Rom Toolbox for any cpu/gpu/voltage configs - just use either voltage control or setcpu - pick one - that is all you need. My WAG here is that Rom Toolbox is not coded to handle our phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwalbach:
What kind of battery hit are we expecting with the OC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
i love that you have the only thread in the original forum. i hope it stays like this. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] appdroid:
well well well look who is here.:p Probably don't remember me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
I'm not sure I understand why. They combined a bunch of forums, which in my view (and experince since) causes tail chasing when someone posts something that is pertinent to a specific carrier, and doesn't specify that.

Now going to more DEV forums?

Sorry...don't reply...off topic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Wow...stable here at 1.9 and it seems everyone else is too! Just awesome!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its pretty awesome. Its my own private forum : D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
Ok - so I am not using Rom TOOL box to adjust CPU settings - but still getting what appear to me to be conflicting settings and readings - I set it a minimum of 341 - but it doesn't appear to stick - see Image in previous post - am I reading this wrong or did the minimum setting change? if so - what would have changed it?

EDIT _ After playing around on the phone, surfing the net - waching a video or two - and then going back to check Settings in SET CPU - the settings are sticking now - - where they were not sticking ten minutes ago - odd -
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
Great work so far....but I don't know what ROM to use. Is waiting for an AOSP/AOKP ROM to coming out this week pointless? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
the purpose of this is because they want to separate the actual "Original" development (Like this kernel thread) from the copy and paste based of some other rom roms that are not original work. its like this in our sgs2 forums also. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwalbach:
How about noop vs cfq and such? Any historical patterns?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
I have no idea but my theory is to not ask and just wait. If it takes two months to however long, IT WILL BE WORTH THE WAIT!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
unless you're going build and figure out how to get aosp/aokp working on this device this week then it is pretty much pointless. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ur doing something wrong. It will show some different setting from time to time as I have stated many times now due to what I thought was an incompatibility issue with the app but here is what I have found from looking at the code and google:

By default the folowing is enabled:

CONFIG_SEC_DVFS=y

CONFIG_SEC_DVFS_UNI=y

DVFS = Dynamic voltage and frequency scaling, which in basic terms is a smart realtime voltage and frequency controller that makes adjustments based on load/needs. It is actually pretty sweet and the reason why we are all (at least so far) are able to OC and especially by such a radical increase (400mhz is just unheard of on SGS2).

Hopefully this will clear up some of the questions on the wierd values we see.

But back to your situation. U got something wierd going on, the minimum should always go back to the real value if your phone is running properly. Try a clear of cache and dalvik, still having problems, wipe!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
You are off to a very good start. Good for you on your private forum ;)

I'm curious what "...original development..." is all about.

I'm holding off on Root and kernels for a bit (waiting to see if my WiFi disconnects get fixed...want to be sure I can return it). But I'll probably be on this kernel if my phone stays with me. Keeping fingers crossed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
Mmmkay. I didn't mean to offend anyone. I just don't know which ROM to use. I'm sure wonderful progress is being made, and I'm patient but if it were to come out very soon, I'd skip other ROMs to use it, that's all. :)

Still, looking for ROM recommendations. I've tried the 2 t-mobile ROMs that uoY_redruM has worked on and they were great. Tried Diet ICS and loved it but another version is coming out soon (waiting for that). Tried Nostalgia 7 and it seemed very clean and streamlined but I had some issues with it. Same goes for ~kyan's ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
f$ck yes :highfive::D:victory::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Underwear:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sulpher:
Least it comes on with the third click... on the damn skyrocket you had to hard reboot :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Deadline seems to be the best bet for avoiding black screen wakeups.

Noop is a black screen machine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Maybe for your s3, I'm running noop with the last official kernel on the last aokp release and Ive seen the black screen one time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
I'm running noop on test Kernel 2 and I've had one black screen since the first few minutes after I flashed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Try intellidemand guys. I get similar performance/battery. Seems to have helped waking up the phone with a few people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DerekPradoFLA:
Thanks for the hard work...... Much appreciated :D:D:beer: cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Try deadline, noop gave me a lot of black screens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I have KTweaker set to apply settings 3 seconds after boot. It requests root permissions about 3 or 4 times before applying the settings. Also, I'd like to suggest adding GPU overclock and GPU governor settings to KTweaker. Once again, thanks for the awesome kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Anyone ever had an issue where they cant hear the other individual when they pick up calls? They can hear me fine but I can't hear them unless I hang up and call back.

Would it be a minimum CPU thing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Could be if you went to low on the screen off profile or just the minimum Mhz in general. Probably just cell coverage though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Try updating your SU binary. I had the same problem on cm10 and updating the binary prevented ktweaker from prompting me for permission on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Anyone else's phone getting wakelocks while on WiFi with this kernel? I checked with BetterBatteryStats and "wlan_rx_wake" is keeping my phone awake for close to 2/3 of it's idle time. I'm not sure this is a kernel issue, but the process shows up under kernel wakelocks, so I figure I'd ask here.

This didn't seem to be happening before I flashed the test kernels, but it might have been, I'm not sure. Does test kernel 2 have different WiFi drivers from the 11/13 release or something?

Google searches indicate that this seems to be an issue with certain types of network security, but I'm on my university's WiFi so I can't troubleshoot there.

I've had a thread for this in Q&A for the past day or so: http://xdaforums.com/showthread.php?p=34679616
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing is dfferent wifi wise, it is just your network, nothing to do with the kernel really. The network is whats forcing the wakelock, not the actual kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
Why? Noop works fine for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Why can't people just experiment with govs and schedulers on their own?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] killman2659:
Maybe I can get help here. I'm on CM 10 and get black screens of death almost every time I lock the phone. Will flashing this kernel make it better?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Fear of the unknown I guess

---------- Post added at 09:56 PM ---------- Previous post was at 09:56 PM ----------

Make a nandroid and test it for yourself ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Thanks but I'm already on the latest SU binary and I have given the app root permissions. My problem is the root access toast appearing multiple times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey Ktoonsez, how come I can't make any changes to this file stick? Do I need to change the permissions on it? I can't increase or decrease voltage from there

Not a problem, just curious.

Edit it's under sys/devices/system/cpu0/cpufreq/Uv-mv-table.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
You don't need to edit the file manually. Use KTweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
KT can you add the file that require CPU spy to work please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
CPU Spy already works, that the only ap I use when testing gov's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
Interesting. I've worked a lot on crushing these bugs and the latest kernels do fix it for me here at work. See the commits that ktoonsez kindly merged in his kernel for details at his github site. I'm interested to know which packets are causing these wakelocks for you. Do the following if you want me to have a look :

1. Download shark from the play store.

2. Change the arguments to -s 64 instead of -s 0 so that I would see only the headers and not the content of your packets.

3. Connect to your work AP.

4. Start shark

5. Close the screen

6. After 10 minutes. Stop shark and grab that shark pcap file from /mnt/sdcard and post it here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
Odd. I installed CPU spy plus and reg and both said not supported. Could it be my ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I know I don't "need to," it's something I want to edit manually. My question was why can't I edit it manually?

Most every other kernel feature can be changed by editing the text files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
U don't edit the file the way it reads. U write back only the voltage seperated by commas. Going from highest to lowest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Could you check mine, I've been getting around 8-10% drain when screen is off using ktconservative/noop, with Wifi on. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
I don't see anything worthy of alert. wlan_rx_wake should be pretty low on your device.

who has ip 192.168.2.4 ? you do have some activity going back and forth between that ip and your phone's. i'd see what's causing that and eliminate it. but nothing from the kernel side that can be done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
That's weird that would be my laptop, no idea why it would be connected. I haven't set any sync activity between them hmmm. Thanks for checking it so fast, I'll keep looking around see what I can find as the culprit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Bizarre....

Just flashed the test kernel.

All of the stock ktoonservative settings work (since it didn't have ktweaker, I'm using the one from 11.13) without any of my bizarre governor tweaks.

Back to ktoonservative/noop for me.

Did get one oddball glitch. About an hour after flashing someone called, and I answered the phone (held it up to my face, so proximity killed the screen) but when the call disconnected, the screen wouldn't come on.

So I just sat it down and watched it for a minute. Screen came back on by itself, no reboot out anything. Unfortunately I wasn't running catlog at the time. I've tried to duplicate it several times since and nothing. I guess if its one-off I can live with that, but I'll put more effort into getting it to do it again when I'm ready.

Catlog shows the attached run of error messages over and over though. When I get home I'll do adb logcat for a while and try to get it to do it again

Edit: forgot to mention, I'm -50mv and oc'd to 1.89ghz. So before I start the adb logcat, I'll drop those variables too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Dang, I need to find that file! I can't remember where it was, it took me like 40 minutes to find that one... I'll keep looking. I remember seeing the comma values one a long time ago...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Sure thing: https://www.dropbox.com/s/7euandodayrf8d3/shark_dump_1354070761.pcap

I'm not sure it's still doing it because I've forced a Static IP address (I stole whatever IP address it was connected as at the time and just made that the Static, hasn't seemed to have ill effects on connectivity so far...) but I'd still appreciate any input.

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
Hooly cr#$! oh man, your battery is going to go down pretty damn fast because your wifi chip is restless. I've never seen anything like this.

You got two issues here and they can indeed be fixed by the kernel:

1. mDNS spam by your GA-tech network that is passing through the filter.

2. IPV6 spam from several devices on the network. Current filters allow for IPV6 broadcast messages to be received, so that's causing a massive wakelock count.

You're getting multiple packets every second man ! It's kinda late here but I can try to compile a special wifi driver for you tomorrow that should be able to fix it. We can then perhaps merge that with ktoonsez's repos.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
Well damn. That's pretty crazy. :laugh:

Thanks for the awesome investigative work man! :highfive:

I'm in no extreme rush to fix this, I mean my battery lasts through the day regardless (it'd just be nice to see the results of my undervolts lol). Take your time getting the fix together; I'm extremely grateful you'd even offer to develop a fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rob116:
I can only imagine that a significant proportion (thoughcertainly not all)of the problems people are describing here are self induced. I've been running these kernels for months now without a single black screen incident. If you have had an incident and you have not first tried returning the clock speed and voltages to stock values, that should be the first thing you do. I'm sure there are some people having real problems,and I'm not referring to you. However, I've heard many people who are complaining essentially say "I'm significantly overclocked and undervolted, why am I getting unstable results", which is ridiculous. And yes, 50mv may be significant, especially at higher clock speeds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
Stock setting or overclocked/undervolted settings. It happens the same... And I don't think I'm alone. Since I've been running the second test Kernel I've had much better time with black screens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
It's not like this has been happening forever. It's only since some of these November builds that we've seen the black screen issue. I had run AOKP 10/21 with the 10/22 build of this kernel for three weeks or so with no issue, undervolts and all.

It's not so reasonable to expect everyone to dial back their tweaks and chill out when an issue unexpectedly crops up in a ROM/kernel update. We know our phones can handle these tweaks. The ROM and kernels just haven't been playing nice with each other recently for whatever reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
So how are you gonna fix it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OTSS:
I'm using CPU Spy to do testing and every time I "Reset Timers", the 1512 MHz does not get reset. Everything else get's cleared...

I tried deleting app data, I uninstalled and reinstalled the app...

If I restart the phone, it resets the 1512 MHz... however it still doesn't clear out when I reset timers.

Anyone run into this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
Yep, only with this kernel. Not really a big deal for me though.

Sent from my Samsung thingy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
My cpu spy clears everything when i wipe stats. On this kernel and aokp.

SGS3 JB 4.1.2 Ktuned Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
SOunds like u got an old version or not using the Plus version. Other version had a lot of bugs and couldnt handle the nuber of steps or the numbers being in reverse order.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
@MdX MaxX

Try the attached dhd.ko file.

Extract the file and replace the one in /system/lib/modules then reboot.

The attached file completely disables mDNS in the wifi filter (even userland applications can't activate it) and also puts more restrictions on the unicast filter so that it will block IPv6 broadcast messages as well.

See if wlan_rx_wake is reduced dramatically now. It would also help if you can do the same thing with Shark and upload a new pcap file here for me to verify that everything is ok.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
I just had the same thing happen to me twice in 5min. It was two calls in a row =/

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MdX MaxX:
'

Well it happens to me undervolted or not, so I'll just deal for now. I'm no developer.

It looks like it works! In an hour of sleep wlan_rx_wake is now about 30 seconds instead of the 40 minutes it was before! I can't thank you enough. :cool:

I'll get a new pcap uploaded in time. EDIT: https://www.dropbox.com/s/vwvbztpm9aebsct/shark_dump_1354145111.pcap
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Can you duplicate it? I spent an hour last night trying to get mine to do it again with adb logcat running and it only did it that one time.

Even oc'd to 2.1 and UV -75... Starting to think it was a fluke on my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
Any way to over clock the GPU?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
You don't want to. Ktoonsez tried it months ago and found that it actually slowed things down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
I'm having the same issue, wiped everything and installed the latest CPU Spy Plus and the 1512MHz timer won't reset. Just an annoyance though.

Also, I noticed using the test kernel you posted that while I can read an NTFS-formatted microSD card, it seems to be read-only and I can't write or modify anything on it even using a root file browser. Is this normal behavior?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OTSS:
I have the newest version of CPU Spy and CPU Spy Plus...

Looks like other people are seeing the same and it's just a kernel thing. That's cool :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Had the same problem with proximity sensor. It was due to too much under volting.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plaut:
Interestingly, if you enable the OC steps in KTweaker, then 1512MHz (and all the rest) do get reset, even in standard CPU Spy (and even if you set your max frequency to 1512).