yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
This sounds like the solution I'm looking for, but is there any downside to this? Shouldn't matter as long as I set the min/max accordingly, right? I'm almost done with my governor tweaking and testing, so this is helpful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yamahakid:
Is it possible that my phone just hates this kernel? No what ROM I've tried it on, this kernel has given me nothing but problems, that is if I xasn even get it to work initially.

I've been doing everything right, I. Just convinced its my device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
Yes its possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Yea man, all processors are different. Had this problem on my One X, could NEVER use a custom kernel, no matter what. But on this and my old Atrix I can do whatever and its all good. The way processors are manufactured causes each one to be unique, and some just get goofy

I understand those are different phones, but as an example I meant that I got unlucky with my one x and got a squirrelly one. People have been reporting issues with kernels not working for a while across all devices (for the most part)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
I give it a shot tomorrow and see what I can do

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plaut:
Not that I know of.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
I've been messing around with the governor and touch booster settings because I felt that the touch booster kept the CPU state close to max too much of the time. By accident, I ended up setting touch boosters 1 and 2 to 648MHz and 810MHz respectively (rather than 810MHz and 648MHz), and I noticed that my phone is extremely smooth and snappy this way. Is there anything wrong with having the first touch booster lower than the second?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing wrong with that, you can set it up however you want that feels the best for your needs. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
Awesome. It's been a while since I've actually enjoyed tweaking a kernel and not had any major issues. Think you could answer my question about NTFS being read-only?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I didnt see it, but the test kernel I put out a week ago had NTFS enabled and it is read/write, probably only with the right ROM though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
Hmm, I'm using task's AOKP. Is it possible that NTFS permissions are preventing me from writing to the card? Permissions for everything on the card shows up as ---r-xr-x and I can't change them using any app. If anything, I'll try reformatting the card again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Hey @ktoon the last I read was about the test kernel 2 I have it and I still get blackscreen upon unlock any advance on that weird issue? if is on previous pages let me know

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nope, I have tried 8 million things, I think its gonna fall on CMs shoulders.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
I noticed that I get the issue a lot more when I drop my minimum CPU frequency to 96MHz. Does upping your minimum frequency to 486MHz help at all?

Also, I haven't been able to figure out this NTFS read-only thing at all. I'm using a Sandisk 64GB microSDXC card and I double-checked NTFS permissions, tried reformatting the card, etc. and it's still read-only in my phone (but not on any computer). I'll deal for now since I mainly use the card for storing music and video and write permissions aren't that crucial.

Edit: After lots of searching around, this seems to be a more widespread issue with microSD cards and the Galaxy S3. Unfortunately, I haven't found any solutions other than buying a different card =/

Edit: BAM http://xdaforums.com/showpost.php?p=34811122&postcount=82
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Yes! I said that a long time ago I set min to 384Mhz I'm a get it a lot less..

---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------

Hey Man I couldn't avoid reading that http://xdaforums.com/showpost.php?p=34811122&postcount=82

I got that 16MB problem With a 32GB SanDisk Class 10 UHS-1 that same problem :eek: I was getting a 16MB partition **** and it can be solved WAO! I already send it to SanDisk to get a replacement because when I got the 16MB partition I couldn't do anything to get it back to 32 or well yes temporary sometimes the memory just worked for a few mins very weird

When I get replacemente I will format to make a unique partition and avoid that problem wao!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
What did you try for getting rid of the partition? I noticed you can't use the partition manager built into Windows, but I'm going to give diskpart a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
As I said I couldn't get rid of that partition never and for now I'm waiting for replacement and I will delete that partition when I get it

Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sihartley:
Stuck at boot screen!

OK, hope someone can help out here..

Running AT&T SGS3 stock Rom : (UCALH9), rooted, CWM 6.0.1.4...

So installed the new kernel downloaded here, wiped cache, wiped davlik, fixed permissions.

When rebooted the phone sat at the ANDROID boot screen, never got any farther! Not a big deal had a NANDROID!

Would have really loved to be Overclocked right now, so if someone could help, please I would appreciate it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atmospher1c:
could this kernel cause wakelock issues? my screen doesn't always come on when i press the power button, but the LEDs for the menu and back button do. i've tried a full wipe and reinstall.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Search is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Try another rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
that's not a wakelock.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
Well, I successfully deleted the partition and reformatted the card, but it still mounts as read-only in my phone (it's fine on all of my computers). Is this definitely NOT an NTFS issue? Because I'm about to send this card back for a refund and get a 32GB card instead.

Edit: Reformatted the card as FAT32 and everything is working perfectly now. On top of having proper r/w access, files and folders with non-ASCII characters in their names are now displaying properly (with NTFS, they were either garbled or not showing up at all). Hey ktoonsez, what ROM were you using while using NTFS? If it's not an issue with the ROM or kernel, maybe it's a combination of NTFS and this particular card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OTSS:
Thank you! This worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I have not used NTFS, it was someone else that tested it for me and he copied a file from and too the thumbdrive with NTFS format.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
Oh, that makes sense. Perhaps OTG is handled differently than the microSD card? I wanted to use NTFS so I could have >4GB files on the microSD, but I'll stick with FAT32 for now since it's problem-free. I've been getting some great battery life with this lately, so I'm happy :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
How well does this kernel play with the recent CM nightlies considering that they are newer than this kernel? Thanks in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It runs great on CM10. Give it a try!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I'm using CM10 stable and it works fine. What version are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
had an issue with the Touchwiz JB kernel today and yesterday, I have moved back to stock for the first time in a couple months, and after installing your kernel was left with a black screen from the time that the boot animation was supposed to show remaining until i rebooted the phone. i could tell that android did load (even though i could not see it) as several seconds after the boot animation the softkeys and the home button responded to touch and gave hipatc feedback and sound, as well as the power button gave hiptac feedback when long pressed as it does when opening the power menu.

i luckily made a zip with the stock JB kernel before i flashed and was easily able to restore it to working order but would like to have custom kernel options.

now about 2 months ago i used your touchwiz JB kernel with the same JB build with no issue. ALI3 (bell stock leak).

would you like me to pull a logcat or do you need a kdmsg ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c_86:
Any news on if youll update this for 4.2 soon? To fix all that sdcard0 stuff... honestly not sure what happens and junk...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Dont need any logs, my kernel isn't compatible with the ROM you are using. That is the only source of no screen that I know of.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Once we release 4.2, a 4.2 kernel will be released :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
Hey, ktoonsez. So I recently had an issue with the AOKP ROM that you and task develop with others I'm sure. However, I wanted to mention, that I greatly enjoy your kernel and the work do for it and the ROM, and your devotion to the android-verse. So in short, I thank you for all your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
in short. you've just polluted our rom thread and then come here to cleanup. good job dude. please don't think about doing that here. :good: :highfive: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
Again, assumptions via a single input of your own. I am on the other hand showing my support for a kernel that functions, and a dev that supports it. Again, consider this conversation concluded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
im embarrassed for you dude. you've now posted in two other development threads that you have nothing to do with nor do you contribute to and you think for some reason its cool? it's actually not over until you leave. I on the other hand will continue to contribute to the community and help to further the development of android. which is the sole purpose of this website. so whenever you decide that you have gained whatever part of your ego back that is necessary for you to move on, great. it will be concluded at that point. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
Does the casted down angel to fight wars, need to step in ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
looks like nate_sheedy has taken a real liking to me. he's even posting in the cm10 about me also. probably to fill an empty void? i'm just popular? haven't quite put my finger on it yet. :D

@ ktoonsez

#trollslovemetoomuch ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
i already caught those an the ones in your thread. Now hes over here? Looks like ill be lining up an infraction if he trolls anymore or fails to cooperate with this request.

NATE_SHEEDY leave task alone an drop the argument now,before i take action on both sides. Task just stop replying to him.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You never said I can't...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Ooops... too late...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
Anyone else getting min/max errors if lock freq isn't selected? Also the widget routinely becomes unresponsive....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Yea.. just leave the locked frequencies checked... dunno bout the widget, I don't use it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Hey madmack,

I noticed today that kernel wakelock "wlan_rx_wake" has been keeping my phone awake 6hrs out of 13 hrs its been on. I was wondering if you could check my pcap to see if you could find whats wrong. This problem is brand new, it started happening yesterday night. I tried reading the pcap through shark reader but it always crashes on me. Anyways attached to the message is my pcap, I let it run for 10 mins with screen off. Thanks in advance. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
I'm free today, hence the quick reply :)

Nothing crazy or kernel related here. You have a high amount BT-AMP packets (google around for more info. Look at Entropy512's posts regarding that) but the bug isn't there on your device. The bug usually shows multiple packets a second in the pcap file. Yours show a burst of packets every minute. We don't have the sources to this protocol so there is so little we can do.

The chatter between your phone and xxx.xxx.2.4 is still there. It's not a high amount but it's something to look after if you want to stop any unnecessary packets waking your device up. Here is a tip, the request is always initiated from your xxx.xxx.2.4 device. I would terminate any background applications if that's my laptop like KIES or any wireless transfer stuff that require a host-client setup. But yea, something in your laptop is aware of your phone and is requesting some crap or simply pinging using the SNMP protocol every 30 seconds.

6hrs tho is so not normal for that pcap file. Perhaps it has been held previously but this pcap doesn't show any culprits for 50% rx wakelock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Thanks for the fast reply. It is very weird, I don't have Kies installed, I only installed the Samsung drivers for the phone. I don't have any sync programs either connected through the phone, all I have done is connected through USB to transfer files. I left my laptop on throughout the night, so that explains why it kept waking my phone. Is there anyways I could find out through my pc whats going on? I already checked the processes, there's nothing out of the normal in there.

---------- Post added at 08:14 PM ---------- Previous post was at 07:53 PM ----------

I downloaded wireshark and I'm reading the pcap, I see that there are a lot of uTorrent Transport Protocols directed at my phone. My phone doesn't have utorrent installed, nor it is paired to my PC's utorrent. I was downloading a torrent throughout the night. It is very weird that uTorrent is sending information to my phone. How do I stop this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
you can try to disable sync and every other program that might use data. Then use the app "betterbatterystats" and look for any activity under "network".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
@ktoonsez

Hey man Idk too much but will any of this non merged fix on CM hellp to fix black screen problem?

Maybe not as you should have seen them already...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Very doubtful, all submitions have been for 4.2 for the last week or so since CM is gearing up for the newest JB:good:.

P.S. Notice anything different about my title??????????????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
awesome work, bought friggin time!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Yes thanks I never doubt about your Title!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
congrats on that!!!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hidea:
A n00b question:

I flashed this kernel earlier today, but decided to return to the stock TW ROM + Kernel (restored an earlier backup, prior to flashing this Kernel).

Do I still need to restore the WiFi + Bluetooth drivers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
No you dont:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Google is the noob question answer. (P.s. I honestly don't know, but I'll race ya to find it faster;))
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
You lose
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
as i said it worked fine without issue over a month ago but if you are not supporting it, that is ok.

do you have any links to your previous versions of the JB TW kernel? i lost the original i had..

if not thanks anyway
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Does anybody have experience with the msm-dcvs governor? From what I have read, it was developed by Qualcomm(which would make sense given the name).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its not that Im not supporting it, it used to work and not sure why it doesnt anymore, something must have changed. I dont have a link to older ones but can see if I have it if you post a date ur looking for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Never was any doubt around here!!!! :good::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
You can try this one... View attachment KT747-Kernel-TW-JB-ATT-10-27-2012.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinichi21:
I didnt see anyone post about the new at&t jb release just letting you guys know the tw jb kernel works on the at&t stock jb :D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Yup! First thing I did after I flashed thr new rom was install kts kernel :) works perfectly after 24hours :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
It's a Qualcomm governor that doesn't seem to work properly in any custom kernel I've used. In KTweaker (for me), it just sticks the phone at either max or min frequency and then stays there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A_Man_Starkly:
CM 10 + kt747 = black screen

Not sure what I did wrong here;

running CM10 (M2)

made a nandroid

flashed kt747 (aosp JB)

wiped cache, dalvik, fixed permissions

rebooted

DEAD SCREEN

pooped bricks

rebooted into recovery (heart attack averted)

Everything is fine now but I'm trying to figure out what I missed, as I saw other people mention that this was playing nice with CM 10, specifically the stable build. I would really like the features mentioned. What am I missing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Which one did you flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A_Man_Starkly:
AOSP Jellybean, sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Maybe a bad download. Redownload the kernel and try again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ForcedZucchini:
So development for this kernel has stipped
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, not sure why you think that. This is the phone i use everyday and I have been hoping CM would finish up CM10.1 stuff and fix the damn screen on issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
KT RAWKS!

Hey Ktoonsez, the first thing I did after using Kies to update my AT&T S3 to 4.0.4 was flash your JB Sammy kernel and it's just beautiful. = I love you maaaaannnn! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Huh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Amazing how quickly people get spoiled by a rapid release cycle...

I'm still docking around with your second test kernel for screen off. I've managed to tweak it to increase the occurrence of the screen off bug, but not really decrease it. Its all being done in end user settings, so I doubt I've found anything helpful.

Really sucks that that all started right before the release that has the lower hotplug for ktoonservative.

I'm still excited about that feature, but I'm running 10-31 during the week because the screen off thing was creating just enough annoyance at work for me to roll it back.

I like to start talking **** right after I get off the phone with an annoying customer and having to occasionally wait to verify the call was disconnected was taxing my self restraint :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
^ beats my stock nexus 7 :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
No. Ktoonsez has a job and is very busy lately. He is waiting to see if cm merges the qcom changes to the main jb branch. If he doesn't ktoonsez will have to re add everything from this to the 4.2.1 kernel because of cm having 8000 old commits in there. He is also busy with the nexus 10 kernel too. Just gotta have patience. It'll be worth it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ejatds:
hi, could someone explain this further? not entirely sure i understand :). if i want to go back to stock (touchwiz), then should i be copying the drivers in the specified folder (the .ko files), and then pasting them back after flashing the stock rom? if i don't do this, what exactly would go wrong?

thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Yup. We were spoiled with an update every 5 days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Nice just pulled a 12700 off hellfire with this kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
What ROM are you running? I haven't gotten the black screen issue at all running Task's AOKP release from 3 days ago and ktoonsez did suggest it was a ROM issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
I still get it (fairly rarely) - tried multiple governor/scheduler combos, I think it's just something that triggers in X circumstances (and who knows what other loaded packages or alarms or whatever could contribute). They'll either figure it out or they'll release 4.2.1 and we won't care any more :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AOSP Test, cus I had 7 black screen today and getting PISSED!!!!!!!!!!!!!!!!!!!

My 4 millionth try, LOL, I am trying again to get rid of the black screen, here you go:

http://goo.gl/DSBpP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatsupnow:
Okay I'm running task's rom let it settle got a few hours then and I flashed the kt kernel I flashed everything correctly followed the instructions perfectly. Now I know for a fact that this kernel just makes everything unstable its terrible, I make a phone call it reboots, I have a few apps going it reboots, I let the thing just sit there it reboots! Wtf? Is there any way to make it stable? Every other kernel works perfectly be it from the tmo side or faux's from here and even the kt kernel from before November worked perfect but now with whatever changes were made it just doesn't get along at all. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
I've been running this kernel since I got my S3 week and a half ago, and the only time I had a reboot was when I try to excessively undervolt. Nothing really wrong with it, runs great and makes my battery last. The only bug which appears from time to time is the black screen when trying to wakeup the phone, which really doesn't bother me much to press the power button one more time to get it working. So yeah, awesome work KT :) haters be haters
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GGXtreme:
Thanks for all the hard work ktoonsez :) I'm not going to try this yet, as I've been going 3 days with no black screen issue, but if you don't mind me asking I'm curious what settings you're running (if not the default settings) so I can try them and see if I get the issue again.

Maybe it's your phone. Not every device can run every ROM/kernel out there, there seems to be a lot more variation in what these Qualcomm devices can handle than with any previous device I've owned.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
196 min

1674 max

486 max screen off

ktoonservative

cfq
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Definately not all phones can do what others can...

96Mhz Min

1728Mhz Max

sio / pegasusq

Screen off 486Mhz

Radically UVed down to 740