yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fizzer82:
Is there a way to flash (or otherwise install) the stock bluetooth driver with this kernel? I'm trying to track down some static I'm getting when using bluetooth media audio (phone audio is flawless) and want to see if that helps.

There is some variability with different governors, voltages, and schedulers, but nothing I've tried, including full stock settings seems to eliminate it completely.

I'm on the Triune rom and this kernel. Tried lots of different combos including AOKP roms, this combo has been giving me the best battery life and functionality with dang near the performance of an AOKP JB rom, just this dang bt issue to clear up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Unfortunately no, when each kernel is built, the correspondint .ko file (drivers) need to go with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J M L:
Yes, it is a ROM issue, not a kernel issue, but the workaround requires changes to the boot.img, which is distributed as part of the kernel. The gsiff_daemon problem* occurs in all GS3 Touchwiz based ROMs, as far as I'm aware. The fix implemented in that kernel seems to be adding the "onrestart restart gsiff_daemon" line to the service zygote part of init.rc:

service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
class main
socket zygote stream 660 root system
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
onrestart restart netd
onrestart restart gsiff_daemon

That would be a great fix to add to the boot.img of the Touchwiz ICS kernel. I have no idea if other things are involved in the fix, that's what I found in the few minutes it took me to pull apart that

kernel image.

*The tl;dr of the gsiff_daemon problem: anytime the phone hotboots for any reason, gsiff_daemon runs away, doing terrible things to the battery. Killing gsiff_daemon will cause it to restart in a normal state. gsiff_daemon seems to be related to using non-GPS data for location information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats what I saw, problem is he reverted it so something wasnt right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fizzer82:
Dang, no user space drivers on Android? It's been a while since I messed with desktop Linux and I'm a total android newb, but I plan to start digging into it soon, so I'm just wondering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] munchkers13:
Ok so every time I reboot I'm getting a core that system tuner pro says it's staying at 2.1gig until I lower them manually... Anyone else getting this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Running new kernel on liquidsmooth and all I can say is saweet so far battery isn't to bad still a lil early to tell need to cycle the battery a couple more times.but great job!!!!! So nice to have it back on my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Ktoonez, could you look at the attached kmsg? I've been getting random SODs on the latest AOKP using ktoonservAtive, sio , a min of 386, and a screen off max of 540. I'm not undervolting or overclocking. The kernel is 10/9b.

Thanks!

Kmsg: http://db.tt/TO9T1WJ2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Try 10/9 regular, not b. B is a test kernel using a different compiler setting that has caused reboots in the past for some users.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its the ROM unfortunately and nothing task and I can really do about it. Something to do with the project butter code. Probably wont get solved until Sammy drops some JB code finally for our phones.

EDIT:

Didnt see you were on the B version. Ya, I have had a few too but was on AOKP 10/9. Nothing yet on AOKP 10/11. Crossing my fingers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Yeah, I'm using the B version but from what I've seen from others who had issues with the -O3 kernels they had almost constant reboots. Also, I'm actually on 10/9 of AOKP. Hadn't checked to see that there was am update today! I'll flash it today and see if it's fixed. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
my phone has been running b sense last night..been running great no problems..subtracted 5mv off of voltages..96mgz 1684mhz..sio and interactive..nothing baf to say at all..thanks again kt

edit..also battery life has been sick..took my phone off charge at 6:30 am..just got home at 9:15 and I still had over 54% with decent amount of usage..not that it applied to anyone else..pretty stoked all together:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Been running "b" version since shortly after it was posted with newest aokp ROM without any issues at all. Cfq/smartassv2 undervolted 150mV from bottom to top(no oc). Of course my phone runs on pretty much everything I throw at it lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] papercutMS:
Thanks for the explaination guys. After doing some reading on XDA, seems like renaming gsiff_daemon seems to be the only easy solution so far. Many have reported no adverse consequences from doing so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pro_b:
Please forgive me if I overlooked something but where is the b version of the 10/9 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vomer:
Lots of chatter on smartassv2. Is it that much better than katoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
He posted a link in the thread, not the OP - search or look back 5-10 pages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vomer:
http://www.mediafire.com/?ypqguk44qhyewdy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
With yours and task latest AOKP, the b version of your kernel is very smooth on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
Happy to report that after 2 days on 10/9b, this problem has not occurred again. Running cfq and ktoonservative 384-1512. Awesome update! My phone is flying!

Sent from my GS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Thought I would post my experience with 10/9b. After boot and use for awhile it seemed fine. After sitting with screen off for awhile, it became extremely laggy to the point of almost being unusable when trying to do anything. (on Task/KT 10/11 AOKP using cfq/ondemand no OC/UV)

Flashed back to 10/9 and it seems to be fixed. I'm going to let it sit for awhile and see if the lagg returns.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Any chance of double releases? Like a stable version with conservative settings, and a "b" version:). for the "sturdier" phones? B is running flawlessly on my phone, haven't had a single hiccup and better battery stats is showing a nice smooth ramp through the frequency steps. I'm getting really attached to it.

---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------

check your processor steps, when I first flashed 10/9b it locked in at my lowest frequency (192). I cleared data on ktweaker, fixed permissions, and it hasn't happened since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
First, I would like to say huge thanks for all the devs and members on this forum for the insane amount of education I have gotten from this site.

I think I have gotten a nice grasp on Android, but I want to ask about flashing kernals.

Is this something you do after your flash your ROM and any other packages? Can flashing a kernal be done any time?

Is this a totally seperate process from flashing roms, etc?

I have searched the forum for a long time and couldn't quite collect up the steps for flashing a kernal. I want to mention I am also almost totally blind so I tend to miss alot of stuff and end up asking questions after hours of searching.

My phone is a Samsung Galaxy S3 model SGH i747M, currently running Slim Bean 2.6.0. (Or maybe custom kernals are included in some of these ROMs?)

Would someone tell me exactly which kernal I should download for my phone, or point me to a thread detailing the steps?

Thank you so much, I know these kind of comments can be a PITA but at times I am forced to ask due to my limited vision.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Answers in the quote... Because you're hard of seeing. :D :p

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
And the kernal I would need for my phone(sgh i747m) is this one?

KT747-Kernel-AOSP-JB-ATT-10-09-2012

I feel like a moron. I used to be a great technician, and was for over 25 years, and now I feel so helpless. It's extremely frustrating.

Thanks again my friend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Yes, that should be it. Since you're already running the rom, no need to flash anything other than the kernel. Keep in mind though, when you update the rom in the future, you'll have to reflash the kernel, after a reboot, b/c the kernel will have been overwritten with the stock rom kernel when you update.

Also, make a nandroid backup first in recovery, just in case anything goes wrong.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
Thank you so much for the information and your patience. =-}
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Don't feel like a moron, this is the fun part :) if we weren't in it to tweak and play and learn stuff we'd probably all have iPhones! I'm a tech too and I've asked way dumber questions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1!

Flashed back to 10/9. Battery life wasn't as good on 10/9b for me and was getting daily screen of death freezes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gfrt94yn:
I have that problem, it's called SoD (sleep of death). I'm not quite sure what causes it; I would assume under volting, but I've tried stock values and still have that problem. Not sure how to fix it however, but at least now you know what it's called
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
I used to spend hours and hours and hours online assisting friends and family with this kind of stuff, and for many years.

Oh, I have an iPhone also. :p Altho I would never own one if I couldn't jailbreak it. I am a themer and a tweaker. I hate stock anything.

When I got my S3(my first ever Android device) I was in love, and you can do so much with it out of the box.

Thank you again my friend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joe772:
Anyone using this on CM10? How much better is it than the stock CM10 kernel? Opinions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
So much better that you should try it and judge by yourself
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joe772:
Is there a mirror for ktweaker anywhere? I can't find one :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Ktweaker comes with the kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pro_b:
Per a short suggestion I got from Ktoonsez, I will pass this along for anyone getting the SoD. Try raising the voltage in KTweaker for your lowest two or three frequencies. I.E. My max is 1674 and my min is 384. I upped the voltages for 384Mhz, 486Mhz, and 540Mhz. Ktoonsez suggested to me to try upping by values of 5 until the issue goes away. I ended up having to increase the default values on my device by 15 (ex from 925 to 940). I have not had another Black screen issue.

P.S. I have a different S3 than I previously had. I previously had a white s3 att. I didn't have to adjust anything and never had a black screen issue. I now have a blue one and I've had to make these adjustments. Just further testimony to the fact that each device is different and settings have to be adjusted accordingly. If this doesn't work for you, please don't flame me. It worked for me so I thought I'd pass it along to help someone else like KT helped me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DudeWatsThat:
I'm gettign random reboots even with loaded defaults.I thought it was my voltages but it's not that since I loaded the defaults and the same thing happend.Any input? I can replicate the problem quite easily using Nozzy, It's not the app since I used it on AOKP and this started happening after I flashed the kernel. I did not dirty flash anything just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinichi21:
Push my phone to 4hrs display and I still manage to get 1 day from It totally phenomenal. I just notice that my wifi problem only happen when my battery is getting low around 10% maybe still on rom side problem. Also I noticed that my ktweaker whenever I try to unchecked the lock frequency it always ask me that my save settings does not match something like but when I leave it check I does not ask again other than that all my settings are sticking. I have also tried clearing the data on tweaker still the same clear dalvik and cache no go the unchecked locked frequency does stick after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
What are your settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerrygooch:
Yes do share! My battery life has gone down the last few releases and I'm in the process of finding out what's causing it. Whether it's an app or something else.

*this was supposed to be a multi quote.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinichi21:
I post it few pages here is the link http://xdaforums.com/showthread.php?p=32674077

And if you guys want to see my first run moderate usage here http://xdaforums.com/showthread.php?p=32667190.

All my widgets are set to 3hrs refresh rate I haven't played with uv yet still testing the stability of bfq and 96 mhz so far no issue I might try undervolting after I finish charging my phone :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evodon84:
Sent you a donation ktoonsez, thanks for all of your great work from the GS2 days and continued work here on GS3 with the kernel and AOKP!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Kt, whatever you did with 10/9b, my phone adores it. Not one single glitch, hiccup, sod or otherwise. End result was by far and away the biggest UV I've ever done on any release and it's rock solid (slow of course, but solid) at 96mhz.

In fact I decided to try to push my luck because it was running so well. Setting my max screen off to 96mhz and set my alarm for an hour in the future. I'd stopped using 96mhz because it would sleep too deeply and the alarm didn't work.

The alarm went off. "Okay" ... I think "so that works, how about this..." I undervolted 96mhz to 900mv. Considering my phone has never worked well at - 25 on any kt747 release in figured that - 75 would certainly cause issues. 2 hours later, I'm pleasantly surprised. Again the alarm goes off.

I figured I'd really swing for the fences, as I always envied the guys that could go down to 750mv. Historically anything under 850 the "apply" button in KTweaker became a reboot button. So I set it at 750, and turned on music player and turned the screen off. Totally expected a lock or reboot as soon as the "max screen off" setting kicked in.

It worked perfectly, 750mv at 96mhz I listened to music with absolutely no distortion, sounded like a cd player, for 20 minutes. So now I'm curious, my phone is well into a place its never been on uv. I start taking 96mhz down - 5 at a time, until I start getting a low frequency buzz on music player at 725mv/96mhz.

Now I'm going to start locking it in at each frequency and seeing how low I can go for each one.

Thank you Ktoonsez! 10/9b is what I was looking for when a first started using your kernel months ago. Sounds like it doesn't help (or even hurts) performance on a lot of phones, but it's magic on mine. Please consider forking the "b" release every once in a while in the future? I absolutely love it.

I'll have to stop here before I start raving, I'm so excited about this... I'd given up on UV altogether
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Awesome man, so glad to here news like that :D:highfive: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evodon84:
You're welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Which version of the kernel do I download if I am running the CyanogenMod 10 Nightly Builds for AT&T?

---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------

By the looks of it from this thread and my research, seems like its the AOSP JELLYBEAN: Download CWM flashable zip kernel, but can someone confirm?

It's one the AOSP I imagine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheWyzeMan:
Well CM10 isn't TouchWiz, so yes it would be the AOSP JB download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DelphinusMinor:
If this helps, I am running Jelly Bean 2.7, and I flahed this kernal. "KT747-Kernel-AOSP-JB-ATT-10-09-2012".

Amazing, my S3 is like a new phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Can someone tell me if my settings for bfq make sense?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -DarthNihilus-:
The rest of my month will be amazing if this kernel played nice with DG's Jelly 747 M6..or any other leak for that matter... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailzfast:
I just flashed the AOSP JB version on CM 10 and it screwed everything up. What gives?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sounds like you did something wrong. That could be what gives. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
I feel ya it worked good for a day for be then started rebooting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailzfast:
Followed the instructions. Wiped and fixed permissions. Got flickering and constant reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
-O3 Test version Touchwiz ICS

Here is a test version for TW users with the cool -O3 flag like the AOSP 10.9b version.

http://www.mediafire.com/?ysv8xv6ti798zyh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Probably a really stupid question here, but which one do I flash for AOKP? Ehehe sorry I'm still a noob at the s3 forums.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
AOSP==AOKP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Yours is a much much smarter question than coming in, flashing the first link you see, then asking why your phone doesn't boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Ahaha noo...i'm not THAT noobish...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Noobs say the word noob
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
And boobs make snarky comments. Everyone starts from zero.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] camoto:
How did you format and choose a file system without using windows??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
http://www.makeuseof.com/tag/format-large-hard-drive-fat-fat32/

It can be done with Windows, and on Mac you can format just about any drive FAT32.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Im not sure how he did it but there are 3rd party apps that will. Probably an easier way though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] camoto:
Thanks for the link! I tried the command line in Win7 and it was complaining about the volume size. I will try one of those tools.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yaotl:
I'm only getting a max of 1026MHz in SetCPU. CPU Spy shows 1512 for about 35 seconds and then never again. Running stock rooted AT&T and the latest kernel here, 7/8. Little help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Do you have power save on? First time I flashed I forgot I had it enabled and it was locked at 1GHz till I turned it off... :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ye that is a Microsoft limitation, nothing to do with the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Yaotl:
hah, yeah, forgot about that. thank you very much!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
Maybe I misunderstood -but the warning in the OP implies that the driver files won't necessarily be included if you flash a kernel - unless those files are in the kernel - can you confirm they are? I was hoping that someone would post the name of the exact files in question so that I could check to insure the rooted kernel I use to go back to stock has the necessary files included. thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
No worries! Glad it was that simple for a fix :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Used all my 8 thanks already..had to go to Tapatalk to thank ya lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
1st hour: Some light emailing, browsing, 1 antutu bechmark, started at 90%, now at 86%! Max 1512, min 486, ondemand & noop.

Sweeeet! Thanks again Ktoonsez, great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Been reading the thread since first post, now that theres a proper version, ondemand and noop seem to be the general choices amongst users... Correct me if I'm wrong...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats what I am testing with. Only time will tell
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
So, in overnight testing of the latest kernel, I can confirm that it's back to approximately what stock does at idle. I lost about 1% an hour overnight.

However, charging is still borked. I'm not complaining, just informing. I've been on the S3 --> USB cable --> PC for over an hour and my phone has only recharged 2%, from 47%-49%.

It doesn't appear that a governor choice would impact this, though who knows. I'm ondemand/SIO 1026/384 with stock rom. I also have the latest cpusleep.apk released either last night or this morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No charging issues here at all. Just double verified, went from 34 to 36 in about 5-6 minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I'm definately gonna check that one out, wanna test without and with though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Forcepath:
This is now working fantastic no drain issues here any longer. Will try charging via usb after lunch and see what I see
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Now I can be really recursive and link to the post that links to the post that has the file that includes the libraries (all from this thread). PLEASE read and search. Please.

http://xdaforums.com/showpost.php?p=28476084&postcount=396
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
Is it me or is this thread missing in the the forum? Had to fins it through my profile
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vomer:
@op - great work on vb (linaro) kernel! I am seeing awesome performance and no hiccups.

Hope you continue to release this version in the future :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Testing now :) what is this flag exactly? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Different linaro compiler setting, should be faster, in theory, but may cause reboots, or has in the past at least.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
Hi guys, I'm having an issue with this kernel, I followed the OP to a T

1.nandroid

2.flashed kernel

3.wiped cache

4.wiped dalvik

5.fixed permissions

6.reboot

phone doesn't come back up, it hangs in the samsung logo, and then it turns off,

I managed to get in recovery by pulling the battery and pressing the 3 buttons(without pulling the battery didn't wanna go into recovery or download mode)

Im on aokp-jb, lh9 modem. Have no idea what i did wrong

here are the screenies of what I downloaded and flashed, and now the phone is kinda soft bricked :(

any help would be appreciated, since i could get into recovery should I wipe and restore nandroid? I dont wanna mess it up even further...