yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Yea I can't download from media fire either. Idk why.

I literally have to use samsung stock browser to do it.. But now I'm running aokp with your kernel :D

Love it

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Good man :D. Cant beat the speed and battery in my book with anything else :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
I know about the desktop mode fix and even that didn't work. Who knows. But I have the kernel and I'm flashing as soon as I get a full battery. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Omg. You don't even know lol. With the jellybean leaks I'd be scared to leave my house without my charger.

Today I went to the gym with 35%.Ran for half an hour. Did some weights etc.. Overall I was there for over an hour and a half. At the end of the night my battery was like 33%. I was like... I missed you aokp :cool::D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
anyone having their gapps stopping alot? i've been getting the message "unfortunately, ..... has stopped" and it's all pertaining to gapps (calendar, google+, contacts) i'm on the task+kt aokp rom (9/24) and latest kt kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Format data, dalvik and reinstall the gapps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slam666:
Hi,

3 quick questions:

1- Can I use this kernel on my S3 on rogers?

2- Do this kernel support phone recording?

3- is it compatible with PARANOIDANDROID (JB)

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbmd:
I believe that all of these questions have been answered in this thread if you were to search or read it.

sent from Task & KT JB AOKP ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Get off of 9/24, there was some issues in the AOKP repo on that day. 9/26 is much better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vomer:
Yes, no, yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadezero:
Hello all,

This is a request for help :(

I flashed : Touchwiz JELLYBEAN: 9.23.2012 Download CWM flashable zip kernel via ROM Manager and now I cannot boot.

I see the Samsung Logo, then the Galaxy S3 logo, then blank.

What would be the procedure to recover from this?

I am running paranoid android 2.13 I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Paranoid Android is AOSP based, not Touchwiz Jellybean.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hedpe:
hey ktoonsez, I'm trying to rebuild a kernel for CM10 but my attempt is failing and putting me in a bootloop. So I'm trying to reach out to a few people who have successfully built their own kernel and packaged it for help. I am able to rebuild it without a problem, but installing it seems to put me in a bootloop.

If you could take a look at my question in the Q&A section I'd sincerely appreciate it: http://xdaforums.com/showthread.php?t=1907854
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadezero:
That's my mistake -_-

I was reading in the thread earlier looking at what users with paranoid had installed. I remember crossing a post that said something about the kernel released on the 18th, etc. I assumed wrong though.

Any chance of recovery? I just purchased the phone 3 days ago... I could go exchange if need be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Reboot to recovery using the three-finger method (search for it if you haven't done it before), then restore your most recent nandroid backup. Fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snwcrash:
Has anyone had experience with this kernel and the Samsung USB Audio Dock? Is the USB audio functionality something that needs to be added at the kernel level or the ROM/OS it self? Currently I'm running the CM10 d2att Nightly Builds + KT747. I read something about the audio redirector, but it doesnt make much sense to me:

Galaxy Dock Sound Redirector by xcaliburinhand

Please have the CM dev supporting your model verify the correct mapping exists between the ROM audio device and the kernel audio path (commonly set in libaudio).

Example: DEVICE_OUT_ANLG_DOCK_HEADSET in ROM should map to the path PLAYBACK_EXTRA_DOCK in the kernel.

Hope this helps. Keep up the awesome work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Answered on your thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I'm noticing some minimal lag on the 9/23 build. Stock CPU, UV'd about 75 across the board. Any idea what could be causing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You answered your own question, too much UV ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadezero:
I'm in recovery, this was a fairy fresh install. I do not have any backups at the moment. Is it possible to flash the PROPER kernel via recovery mode to make it work?

EDIT: Everything works great now!! Thanks for the tip!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Hey ktoonsez. Not sure if it's aokp causing it but I notice the touchboost don't stick.. My first touch I set it to 1080mhz. But when I press the screen it jumps to the max cpu I set it too (which is 1242mhz)

I'm gonna do a fix permission in cwm again to see if that fixes it. But just wanted to let you know

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ill bet you 100 dollars your on ondemand governor ;). Here is part of the changelog:

2. Added way to disable Touch Booster (its under First Touch Booster to disable both) (Doesnt work for ondemand for AOSP version since CM has there own version of Touch Booster)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Ah shouldve read that lol sorry.

But I just did a fix permission and now my sdcard is corrupt. Wants me to format it and now I can't access it -_- any fix to that? Or am I gonna have to reflash rom

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Id try reflash the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Ah, thanks. I was running the same voltages on the previous build and it ran totally smoothly, so that's why I asked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BiggDavin:
The way I've permanently fixed the corrupt sd card issue is by formatting the card as fat... I'm using a 64g card, not sure if that was the cause, but I haven't had an issue since formatting it to fat.

This WILL erase any data you had on the card!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Dam.. It really corrupted my sdcard. Can't even open it in my computer. Reflashed the rom and everything. ****. Do you know of any way I can retrieve all my music from there? That's all I have in there

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
If you can get the sd card (external?) into ur pc use pandora recovery (its free)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fvargasfrank:
I don't know if it Ben reported but on this last version bluethoot is no transmitting music, the phone audio is fine but pandora and my music player will only play thrue the phone and no my stereo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Been reported, depends on the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
Got my 64GB today... had to format to FAT32 to work... by default it formats to exFat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I've noticed that my phone is perfect with the task+kt aokp jb rom (9/16) and kt kernel (9/13). Other rom and kernel updates makes my phone freeze and reboot like crazy. Is it just cause of how my phone is? Or am I doing something wrong?

these are the steps I do for each update:

1. Wipe data/cache

2. Wipe dalvik cache

3. Install rom and gapps

4. Reboot

5. Recover google account info

6. Reboot to recovery

7. Flash kernel

8. Wipe cache and dalvik cache, and fix permissions

9. Reboot system
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
steps are fine, but try it like this:

Wipe Data / Factory Reset

Wipe cache

2. Wipe dalvik cache

3. Install rom and gapps

advanced => reboot recovery

7. Flash kernel

8. Wipe cache and dalvik cache, and fix permissions

9. Reboot system
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
unfortunately, it even freezes during the welcome screen :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
does it seem like things dont run properly until you've restored ktweaker's settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
even with ktweaker's settings restored, i still get freezes that would require me to press and hold the power button to turn off and turn on again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Try the 9/26 AOKP ROM with the stock kernel and see how it runs. I have run into this myself once or twice in the past when the CM kernel has been updated (as in the last two ROM updates) until ktoonzes updates his kernel with all the changes. Not sure of that makes sense to anyone but its happened to me. When it does I just run the stock kernel. Not saying there's anything wrong with the kernel it just doesn't play well with my my phone sometimes in that situation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Genomerio:
I have tried going over past posts and searching but the thread is so big I havent seen anything related, so here goes.

Have a 2 week old S3 from AT&T. On rooted stock touchwiz. On the stock kernel I didnt have any real issues, was just looking to try a differnet one for battery life. Installed kt, and even on default settings with the ktconservative gov. Battery was noticeably better. Pretty happy with that. However, I noticed when I plugged the phone into the car (headphone jack mod for my older car), I had a ton fo pops and clicks on audio playback. Verified it is not the cable in the car, as the sounds are audible on the speaker, as well as 2 headphones. noises only happen on sound playback, on both mp3 and ogg files. Grabbed the rooted stock kernel in the OP and flashed that. After clearing cache/fixing permissions booted up and audio was just fine. However, now my wifi would disconnect every minute or 2. Reflash kt and wifi works fine, but audio clicks and pops.

I did the full cache/dalvik cache clear/fix permissions each time.

Any thoughts? I like battery life, but the audio playback is unbearable. From what I have seen, looks like I am going to have to reflash the stock ROM to get things back to normal/stable unless anybody has a suggestion.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
what is your minimum frequency and voltaqe set at?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Increase your minimum speed - and yes, it's in the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Genomerio:
I have not changed any setting. It is running stock voltage/minimum speed. 384Mhz, 925mV

*EDIT*

I upped minimum speed to 425Mhz and it appears to have removed the audio issues.

Sorry for the repeat question, I just did not see previous replies about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I'll give it a try.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monk33y:
If the card is not readable or recognized by a PC you might have to Low-Level Format it. There are a few utilities out there that can do this...

HDDGURU is one... :D

Unfortunately you would lose all data on the card... :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Gotcha. After much playing around with kernels and rom updates, I found that the most recent task+kt aokp jb rom (9/26) works best with kt kernel (9/18) on my phone. So far i was able to actually have a functioning phone without any freezes or reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I mean it's readable I just can't access it. Only choice I have is format. And i don't want to lose all my music.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seh6183:
I've searched this thread and saw that others were saying MHL was working by using this kernel and AOKP. I'm using that right now and I can't get MHL to work no matter what I do. Is it because I'm using the JB AOKP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatclaw:
I have a major problem that I can't figure out how to get out of, although I've searched the forums for a remedy until my fingers bled.

I was helping my brother flash a CNA and this kernel, but I screwed up bigtime. Although I don't post much, I mostly know what I'm doing as I've been very actively involved since the Captivate in '10. I sent him the links for the Rom, kernel (this kernel), and gapps, and instructed him what to do. Unfortunately, I sent him the link for the ICS AOSP version, and not the Jelly Bean version which was obviously needed for CNA. I was just in a hurry and didn't pay attention to the link that I clicked to get him the D/L url. After he installed everything in recovery and hit reboot, the phone basically turned off and is not showing any signs of life, nothing on screen, no sounds, and no vibrations of any kind. And getting into recovery/download mode is a no-go. The only thing happening is that the computer looks for drivers when the phone gets plugged in, but Odin is not picking up on it.

This sucks, he trusted me and I'm thinking I bricked his damn phone. Obviously it was 100% my fault, and I will make it right even if I have to buy him another one outright, but I'm hoping that will not be necessary. Is there any way out of this, and would it be pointless for me to even order a jig? A big thanks to anyone who can help me, I'll send a beer or 3 your way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
SO he is not getting the SGS3 splash screen? If that doesnt come up then it is bricked (should NOT be the case unless he is on another carrier and not AT&T). Your best option is to send it to get jtagged to see if it will come to life. Let me know the status.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatclaw:
First off, that you so much for your quick reply. Its greatly appreciated.

He is on AT&T, and there is no splash screen. Just a whole bunch of blackness. That's what puzzled me most. I do know he flashed exactly what he was told to, by me, and it was most definitely your AOSP ICS kernel. I actually made him take a screen shot of what he downloaded, so I know exactly what he flashed. Just stupid me missed the "ICS" in the file name. He came from stock rooted, formated data, wiped everything, flashed GNA JB for ATT, then gapps, and then your ICS AOSP kernel. Then when he hit reboot, it was like the phone turned off. I thought it was weird because its not like I never flashed the wrong kernel before, albeit not on this phone though. Was always able to worm my way back into recovery or D/L mode. Just pisses me off because I kept reiterating to him to do everything as I said it, and it was my dumbass that screwed his phone up.

What exactly do you me get jtagged? I assume you mean to send it somewhere? I'm in New Orleans so I'm guessing there is nothing like that locally.

Thanks again by the way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Your welcome. JTag is a special process that loads stock bootloaders, ROM, kernel, everything. This place is a good place to send it (tell him task650 sent you there):

mobiletechvideos.com

With no splash screen that means the bootloader is toast (Usually) which is hard to believe that it is messed up by NOT flashing anything in Odin other than a "Recovery". Looks like you have had him do the 3 buttons to get into Odin and or Recovery? So I would say that Jtag is your last option really.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatclaw:
Yep he sure did, tried everything. And I know he didn't flash anything crazy in Odin. I will go pick it up tonight and pop my battery in it just to see if what happens. Although he had more than adequate battery when he went into recovery, he was in there for the better part of an hour due too interruptions. Maybe there is a slight chance his battery just freaking died in the process?

Well if I can't get anything else to work, I will definitely send it to your referral. The last thing I need right now is to break the news to my pregnant wife about how I need to drop another $600+ on a phone when mine is not even broken! Also, I'll send a few more beers your way, for your help with this and the pleasure of rockin AOKP and your kernals over the last couple months (on my phone, unfortunately not his).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psloan:
Hey ktoonsez,

What modem are you using for wifi for the kernel? I updated to the latest build (UCALH9) for the stock rom from the instructions here

http://xdaforums.com/showthread.php?t=1896773

I used the "pieces" method to apply only the rom from that thread. then I applied the updated modem to the UCALH9 modem. when I boot I could no longer activate the wifi. Tried a number of clear cashes, fix permissions etc.. still no go. So I reapplied your kernel and now the wifi is working.

The modem i tried was from here:

http://xdaforums.com/showthread.php?t=1831898

Thanks.

--pat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Whoever made that flash file must be flashing more than just a modem then, thats what had to have screwed it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
I made those files and the ROM pieces file flashes only that. It does not flash /system/lib/modules, which is why it didn't work until a kernel was flashed. The instructions explicitly state that you have to flash a kernel after flashing the ROM piece.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
Love battery life like that....

Sent from my Nunified S III running Triune II
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
What was your screen time on that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Not sure what happened on the 9/23 build, or may be prior, haven't messed with UV in a while. But I was just playing with it a bit today, and I have 144 and 192mhz down to 750mv and its running great. Alarm still goes off from deep sleep and everything. Gonne step down another -25 in a couple hours and see what happens.

My phone wouldn't tolerate more than a -5 UV last time I tried it, so calling this an improvement is a pretty epic understatement. Once again, great work KT! Loven it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadyraver:
Data Switching

I'm running Ariel rom with Koontz Newest TW Kernel..It seems like it is having a hard time switching from Wifi fi to Lte and vice versa...I'm coming from stock everything and there were no problems before...Actually now what I do is I turn Airplane mode on and off to switch between data connections faster..What I was wondering is if there was something I can do or change in the Kernel or some other settings somewhere where I can get the right data connections to switch and lock on correctly at the right time??

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I have this weird issue with your kernel and the Facebook app. I'm on aokp and I've tried it with the stock kernel and everything is OK. But when I flash your kernel if I browse pictures in Facebook app it kind of reboot but it takes me straight to the boot animation no Samsung or galaxy s3 as usual boot. I did not change the voltage and I have tried without oc and uc and it still happens. Anyone know what is going on?

Everything else work great so it is no big deal . Also when I use Facebook via the browser it doesn't happen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Is it safe to assume that you've wiped cache, dalvik and fixed permissions a couple times since you flashed the kernel? I'm running the same setup and no issues at all with Facebook.

Sounds a lot like a broken permissions problem, but to be safe, I'd redownload the kernel, flash it, wipe cache, wipe dalvik, fix permissions, reboot recovery, fix permissions again. If it still happens, wipe Facebook's data, if it still happens after that, uninstall and reinstall Facebook.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I did wipe cache, dalvik and fix permission several time. I redownloaded it tonight and I flashed it with the latest aokp:I formated everything, flashed rom and gapps, reboot to recovery,wipe cahe and dalvik, flash kernel,wipe cache and dalvik plus fix petmission and rebooted but the issue is still there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Did you use any backups after flashing? Like titanium backup? To restore any app data?

Does it happen on any photo or just specific ones? I'm doing everything I can think of that involves Facebook and photos amd my rig is ticking like a swiss watch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
No backup at all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Damn... I'm sorry, but from what you've told me, sounds like you should be the last person to have issues. I'll keep thinking and pm you if I come up with anything else, but it sounds like you're running this by the numbers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Haha I know! I really don't understand since I run aokp and kt747 kernel for a few months now and never had this issue. It appeared in the last two release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Yeah, its pretty clear you've been following the threads. You've done everything I've read or learned about dealing with issues on the ROM and the kernel. Wish I had something helpful to offer, or at least a similar issue, far as I can tell you know at least as much about this as I do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sidneymac:
I'm on 9-23 and I notice cell standby using 50% of usage. Rom is stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sidneymac:
Is there anything related to the kernel causing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloudyphiz:
That looks like incorrectly reported cell usage, if you're at 70% more than 11 hours after charging then it's highly unlikely your cell usage is really that high. Unless you basically never had the screen on, or you had no network signal for a large part of the day. Neither of which anyone can see from the single screen you posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
It is normal , your phone must have been in standby most of the time. The 49% only mean the cell standby used 49% of the 30% battery draining. It seems fair to me after 11hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
Screen time was 1 hour 42 minutes or so....

I noticed a lil more battery drain with the 9-23 over 9-13 but still a great kernel...

Sent from my Nunified S III running Triune II
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sidneymac:
Now at 49% the cell standby used 41%..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I do not see any problem there. Try a screen off profile and try some more governors. It may reduce the standby use of battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
I'm just jumping in here, not sure if anyone has mentioned this, but this looks like the cell standby usage bug. Are you stock? Some stock firmwares report cell standby much much much higher then it actually is, it's supposed to be a value of 3.4mah or something close to that, but the bug is its listed in the phone as using 34mah..sorry if you already knew this. Most custom roms and the newest att ota have this patched, there is also a flashable fix floating around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
Has anyone expierenced random reboots while on the net? Happened yesterday and today with 9-23

Sent from my Nunified S III running Triune II
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sidneymac:
I'm on stock... latest from Samsung. And I'm.aware of the bug from the phone's initial release. Also I'm overclock to 1809mhz and UV.