yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Got it, thanks! I'll let you know what I figure out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Thanks DM. I haven't tried to clean flash, because I have no time for the next 2 weeks. Dirty flashed SlimKat 5.6 (cleaned cache, dalvik and formatted system), ditto for latest DKP, then installed Viper audio (which isn't engaged for bluetooth). The same crash occurs without Viper installed.

The dialer works fine, with or without bluetooth on, and calls are clear. But if bluetooth headset is connected (no issue with wired, which works fine), the dialer launches to a blank screen and then freezes the phone until either the OS offers to close it, or until reboot. If bt headset is connected during a call, the call freezes the same way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SomethingAwesome:
Hey, I'm liking this mod so far. Only used it for a day or two, but it seems to be smooth and not using much power. I'm getting some audio bugs with PowerAMP playback. Basically just randomly starts outputting super high-pitched tones at full volume (does this over either headset or built-in speaker).

On CM 10.2.1 stable/final running on a Canadian 747M. I'm running the 2013-12-26 Test Kernel as it seemed to be the latest version for ASOP 4.3. (I also tried the stable)

Maybe I should be using a different version?

Cheers, and thanks for the hard work!

:beer:

Sent from my SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Same bluetooth dialer crash on clean flash

Just clean flashed - still the same crash when trying dial or even launch the dialer while connected to b/t headset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I haven't even thought about AOSP 4.3 since the 12/26 build. :o

Processor voltage issues have been known to cause problems like this. Even if you haven't manually lowered your voltages, (IIRC) dkp builds back then defaulted to using reduced processor voltages. dkp uses a ridiculously complicated system for determining processor voltage, but it means there's an easy fix: download dkp-vmin-XXX.zip, rename it to dkp-vmin-1150.zip, and flash it. You might even be able to get away with using a lower number; I've heard anywhere from 850 to 1050 recommended.

I'm still digging thorough all the BT stuff to track down what's wrong. Unfortunately, it might take me a while; there's a mind-boggling amount of code required to support BT. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
I really appreciate your efforts!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] biglilsteve:
Anyone else having issues with the file hosting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
A few people in the Sprint thread are having issues too. I'll see what I can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CheateR92:
Is it possible someone to share the latest kernel until dkp host is fixed?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I don't have an ETA on the hosting situation, so I'll resurrect the old MediaFire mirror. The last two AOSP builds are available at http://www.mediafire.com/?jlehejjarshqd

I can't mirror TW at the moment, but I'll get to it later today.

EDIT: Forgot I was supposed to upload TW. TW 4.1 & 4.3 are up at https://www.mediafire.com/folder/9nc6cmdzmb8km/dkp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] biglilsteve:
Thanks much, sir.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
So, after clean flash, problem persisted... Until I wiped data for Dialer and Bluetooth Share apps in App Manager. I had restored data for each with TiBu... Silly in retrospect.

Also learned that I can't live without bluetooth earpiece.

Thanks again for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Scratch that. Just had another freeze and crash, deleting app data didn't fix it after all.

Tried the routine again, doesn't fix. Back to the ole drawing board.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CheateR92:
Is it fine to flash to 4.4.3? I believe it is but I wanna be sure that dkp is compatible before flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just make sure you flash the latest dkp release after 4.4.3 and you should be fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
I'm running cm11 0604 nightly and latest dkp, but I've been having a lot of reboots and power offs. Can anyone interpret this last_kmsg?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
[ 3237.694673] Unable to handle kernel NULL pointer dereference at virtual address 00000004

decimalman will have to look at it himself. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Curious that it worked once, though. :confused: I will confess to being thoroughly puzzled by this.

Thanks for providing debug information. :good:

Were you using the freelunch governor (or possibly performance) at the time? It looks like a governor attempting to wake core 2 up is causing the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Freelunch. It seems like it happens immediately after I turn the screen off.

This is with mpdecision left on in trickster.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Lunch isn't free anymore. You'll have to pay... with a reboot! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
If I wanna flash M7, which version of dkp should I use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks. I'll take a look through the freelunch code and see what I turn up. It's overdue for an update anyway.

6/2 should work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So has 6/2 been pretty stable with the last few CM 4.4.3 nightlies? I'm thinking about flashing tonight, but I can wait if there are problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1 flashed 4.4.3 but waiting for kernel confidence ☺
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
It's stable, but battery life and "smoothness" seem less to me since 4.4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bmeek:
I found that dkp 6/2 works well with the cm11 6/8 nightly build. I hit some issues with subsequent cm11 builds (6/11 & 6/12), but the issues don't seem to be kernel-related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DMF1977:
Love this kernel, but it wouldn't even boot past the splash screen on task's latest 4.4.3. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirbymaster101:
Any con to having fast charge always enabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thantos:
USB data transfer is lost
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
To be more accurate you can't transfer data over a USB connection if you have fast charge enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scorpionhd2:
But on the pro side to that con, you can toggle the fast charge on and off as needed for data transfer with TricksterMod easier than pie. I do it all the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
uhmmmmmm.....trying to download from alternate site (not mediafire), the latest two builds give me this...ummmm....could a different link be provided? or maybe its just my phone/location. i was able to download older builds (4.3).,but i was looking for 4.4.x.

any help/suggestions would be appreciated.

thank you

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] balrog558:
I had the same error. Ended up just grabbing it from media fire, worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
thanks. will try again.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
There's a new AOSP build up on MediaFire. Changelog:

Synced with CM: tons of updates from CAF, also switched to the ND8 (Sprint KitKat) wifi driver

Re-enabled some GPU settings that disappeared a while ago

Rewrote my changes to the wifi driver to support the new code. If anything (wakelocks in particular) misbehaves, let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
hate to ask, but i am really having trouble with mediafire.

any chance you could provide a dev host link.

thanks again for sharing your work.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
http://d-h.st/oB5

Is Dev-Host still flaky? I stopped using them because they were somewhat unreliable and had started sneaking sketchy APKs in with legitimate downloads. :( If they've sorted that stuff out, I might set up my build script to mirror to both MediaFire and Dev-Host.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
i'm unsure about sketchy-sneakies sir, but i was just able to download dkp-aosp44-d2-20140705 without a hitch.

thank you again for your time/knowledge/work. flashing now.

:good:

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoryB:
On our phones it tries to download MobiGenie.apk or something like that. Some blockers prevent it, but I do not use them so I have to stop the download and be careful what apk files I pick to install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Androidfilehost is pretty nice IMHO. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Hello. What I did for media fire to resolve the blank download page was install dolphin browser and used that when I clicked the link in the op.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Seconded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Latest AOSP dkp kernel seems to be running fine on CM11 M8, in case anyone was wondering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobchef:
I just tried to download from the devhost mirror that was just posted, and was offered mobogenie, then when I pressed cancel I was redirected. I am not using any protection tho:D

Sent from my baked potato
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I finally got everything merged and working again (some weird compiler misbehavior was preventing everything from building), and there's a new AOSP build up on MediaFire. Changelog:

Merged everything from CM. This includes changes to the wifi driver that probably won't work on ROMs before 7/23!

Linux 3.4.99 and BFQ v7r5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Thank you!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Possible dumb question. The kernel is not flashing a splash screen. So my old kernel screen is showing up. Is there a way to change that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
hi,

I use 3.0.31-dkp-geb13439 Mar 20

is there recommended update for this version for TW 4.3?

anything for TW 4.4?

the reason is that waze just power off my phone :crying:

How none root app can turn off power or make it so bad?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
[MENTION=4932679]decimalman[/MENTION] thank you for your hard work. Your tw kernel is the only one close to stock! Will there be a new kernel for 4.4 in the future? I'm holding up my upgrade to 4.4 just because I can't find a better tw kernel. Also do you mind to compile a copy with uksm off by default? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
Anyone knows a working 4.4 tw kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Sorry to mention other kernel.

KT Kernel base on Sprint source work perfect with two 4.4.2 on AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Safe to flash the latest build with CM11 M10? Last dkp was from late July, so I'm not sure if there have been any kernel commits on the CM branch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No, not safe. There's been changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
That's what I figured. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
Kt doesn't support faux audio, uksm fsync etc. It just a stock kernel with additional governors and UC voltages. I'll see if I can make a kernel based on nf6 stock and adding the some of the decimal stuffs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I read that the source code of NE4 was already release by Samsung.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dirkdigles:
True statement

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I guess I should check my threads occasionally, huh? :o

There's a newer TW4.3 build (20140515) on MediaFire. I still haven't put together a build for TW4.4.

As for Waze causing problems, I'm not sure what would cause that. If it's hitting a severe enough bug in the kernel, it might cause an automatic reboot. If it's still happening on the newest dkp build, will you send me a copy of /proc/last_kmsg after it happens?

I'd like to do a TW4.4 kernel, but I haven't had a lot of free time or brainpower for dkp recently. TW4.4 (finally) switched to a 3.4 kernel, which is causing a lot of conflicts and means a lot of TW-specific workarounds need to be rewritten.

I generally don't like doing custom builds for small configuration changes like disabling UKSM. Last time I checked, Trickster didn't have an option to disable it, but other apps do (e.g. Performance Control). I'd recommend leaving it enabled on TW though, since it generally saves several hundred MB of RAM.

There have been some changes to the kernel since the last update, but they shouldn't break compatibility. I haven't pulled in the changes yet, and recent CM nightlies are still working fine for me. M10 should work fine as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Okay. I might try it out, then. Any plans on pulling in the changes and releasing a new version of the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Ask and ye shall receive. I meant to release a new build a few days ago, but I got distracted. :p

There's a new AOSP build up on both mirrors. Changelog:

Synced with CM, and got Linux 3.4.103 in the process.

Fixed mpdecision detection. It was causing mpdecision and auto-hotplug to continuously fight on newer ROMs.

Added a bunch of tiny optimizations that shouldn't have much noticeable effect.

Possibly updated some stuff related to GPU OC? I don't remember what was included in the last build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Thanks, decimalman!

Quick question. I can't remember whether or not MPDecision should be left enabled for this kernel, since it has auto-hotplugging of its own.

Just flashed the newest kernel build with CM11 09/25 nightly and everything seems in order so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
09/25 has an unusually long boot time on the latest CM nightly, and I'm not too sure why.

I'll grab last_kmsg if I experience it again (currently waiting for the recent AOSPA build to be uploaded).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NightHawk877:
I've been waiting patiently for a new release. Little did I know it would be on my birthday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Hey decimalman, u gonna show us some tw love too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's no such thing as a sentence that contains both TW and love used in this manner. :p

I gotta test 4.4. I imagine it wouldn't be terrible once debloated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
TW is on the rise lol give it a shot a couple great roms out now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It's fine to leave it enabled. dkp automatically switches between mpdecision, auto-hotplug, and governor hotplug as needed.

I think I know what I did. I'll revert the change and see what happens.

Happy birthday!

I don't care for TW, so it generally doesn't get updates as often as AOSP does. A TW4.4 build will happen eventually, I just don't want to run TW for long enough to actually put one together. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Hm. I haven't noticed anything like that so far. Running latest dkp with CM11 9/25 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Alright, ran into my first problem with the latest release, and it's a big one. I'm on CM11 9/25, and every single time I try to stream a song to my car radio via Bluetooth and then lock my screen my phone reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
That's not good. Does /proc/last_kmsg show anything after the reboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I know this isn't exactly dkp related, but I've had my first weirdness today with the 9/25th nightly running the stock kernel. I turned on my screen and I couldn't press anything on it to type in my PIN. I long pressed to bring the reboot menu, it did, but there I couldn't press anything either. Turned off the screen and back on, still nothing. I had to force reboot by holding the power key for 10ish seconds.

So your mileage may vary, but this might not all be dkp related. Just throwing that out there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I switched over to leankernel for the time being, and I'm not having the Bluetooth problem. When I'm back in my car tomorrow morning I'll flash the latest dkp back on and try to reproduce the issue. If it happens again I'll upload the last_kmsg.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks!

I think I know what's causing it (or at least I found a bug that causes similar problems). I'm going to do a little more testing, and if all goes well, I'll post a new build later tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I flashed back to the 7/26 dkp kernel for the sake of testing with the 9/25 nightly of CM11, and I haven't had any issues so far. So it definitely seems like an issue with the newest build, or maybe something that was merged from the newer CM stock kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I reworked the problematic commit, and I haven't been able to cause any reboots since. There's a hopefully-fixed build here. When you test tomorrow, will you try that build instead of the "official" 9/25 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
My phone freezes and reboots during Google Play Music. I will go back to the July update for a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Currently streaming Pandora to my Bluetooth shower speaker with no reboots on this build. I still have to test it in my car, but it looks like whatever commit you removed may have been the culprit.

Edit: One remaining issue is that when answering a call over Bluetooth neither party can hear one another. I had heard about this issue with recent CM builds using the stock kernel, so once again this issue probably came along with the merged CM commits around the time you compiled this latest dkp kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
CM said kernels based on 3.4.103 are the one affected. I don't remember learning if the next successive Linux version fixes the issue or not, and whether or not that buggy version only applies to CM's kernel.

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, that's all it is. Any kernels built from that CM base are gonna have the Bluetooth issues. Luckily the 7/26 dkp kernel is working just fine with the current CM nightlies for me, so I have no problem sticking with it for the time being.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Try the test build I linked a few posts back. The bug I fixed was pretty general, so it will probably help.

Great! :) I wouldn't expect your car to cause any more issues than any other BT audio devices.

It doesn't look like 3.4.104 will have a fix, though I haven't merged it yet. I'm not sure I'll be able to actually fix this, since I don't have many BT devices to play with, but I'll take a look around anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Running dkp on 26th nightly. Runs well. Good job, as always. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikek753:
can dkp aosp 4.4 be used on NE4?

hello,

I already flashed NE4 (modem) to my S3

can I load new AOSP DKP on NE4?

thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
Yes.

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I promised a user I'd put out a new AOSP build today, so I guess I will. It's up on both mirrors.

Changelog:

Merged the latest commits from CM: Linux 3.4.104 and a fix for the BT headset issue

Built with a shiny new GCC 4.9 toolchain

Added a new, wildly experimental CPU governor that I've been playing with for a couple days*

Switched to 120 Hz timer frequency as an experiment

* The new governor is called "tierservative" because it's vaguely similar to conservative, except it uses frequency "tiers," and I'm not at all creative. :p It's nowhere near finished, but I expect good things from it in the future.

EDIT: Looks like MediaFire just took down the latest build, and I can't get it uploaded again. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
So I've been playing with tierservative some more. I removed a bunch of stuff that didn't make sense (ramp delays), was completely useless (hotplug notifier), or actively hurt performance. There's a new AOSP build up on both mirrors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
What is exactly is freelunch governor? Please be as detailed as possible. Also, would this work with Quantum 5.2? I thought I heard somewhere about data issues with older roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Read this:

http://xdaforums.com/showpost.php?p=40084120&postcount=3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
Is "/sys/devices/platform/mipi_samsung_oled.513/lcd/panel/panel_colors" still the correct target for changing to Trinity colors?

I couldn't find the "file" when browsing /sys, so I was wondering if the info on the first page is still relevant.

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Thank you! But does data work with this kernel and Quantum 5.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
The panel_colors file disappeared when CM added gamma control. I didn't want to rework the patches to integrate the two. I don't remember where I saw it, but there's supposed to be a way to enable Trinity colors using the gamma control settings. I'll look for it tonight and let you know.

I don't see why it wouldn't. AFAIK, there haven't been a lot of compatibility-breaking changes in the kernel lately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJohnson1988:
Ah, okay then. BMS uses the gamma control technique you speak of.

I have the following in init.d:

#!/system/bin/sh

echo "60 60 60" > /sys/class/misc/gammacontrol/tuner
echo "60 60 80" > /sys/class/misc/gammacontrol/v1rgb

Should do exactly what you want.

Samsung Galaxy S3 (AT&T)

i747UCUFNE4 baseband/bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I just installed aosp kernel on my d2at&t running task650 aokp kk, I am getting random freezes. Any suggestions? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Take into consideration that tasks rom is no longer in development and for what I remember last couple of KK versions he released had issues that never got resolved (correct me if I'm wrong). With that in mind also make sure that the kernel version that you're installing is compatible with the ROM release that you're using...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Thanks for the tip. I have the 7/29 version which I find is stable. I'll try an earlier version. Thanks again.