yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halodos:
Thanks, I was just thinking of the performance governors where the frequency locks at the highest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
At 23 hours with 30% remaining, moderate use. On screen 3 hrs. Almost 4. Let's see what this baby can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Dude your signature is sick!!!! :laugh: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Yes it is... Wonder where he got that from???? :D :p

It's OK, I borrowed it from someone on Rootz; just didn't like the square edges, so I gave it a bezel and added the drop shadow. ;)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Gotta thank [MENTION=3812527]Swiftks[/MENTION] for that. Signature is the sh**.. So I had to copy him. (; Best ROM, with Best KERNEL.

Thanks [MENTION=3357040]Imoseyon[/MENTION].

& Thanks [MENTION=3812527]Swiftks[/MENTION]. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
where's the mpdecision option? i don't have it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
Right here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
LOL i don't know why i've never seen it before. Very nice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I laughed, cause you know it can't be more obvious. Unless you don't know about Trickster. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
I disagree, I found it very difficult to understand the menus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think the options are scattered a bit randomly, but if you're curious enough like you seem to be, you'll be able to find what you need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
well... i don't have it. is it on nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You have to flash learn kernel and use Trickster Mod you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
lean kernel 7.1 stable is running on my device now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
Maybe it's a premium feature
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
what is the advantage to have this option disabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
MP decision doesn't try to revert the CPU & GPU to the predefined states.

There's some settings (frequency, governor, governor tunables) that get overwritten by MP decision depending on what you are doing (screen on/off, cpu load, gpu load, thermal sensor value etc) and when you are overclocking or manually changing some CPU or GPU settings this is no good since they won't get applied or will get applied until MP decision decides to act up.

It's best to have this disabled if the kernel you are using can hot plug a different way (Lean kernel can't), and in the event that it can't it's important to enable frequency lock (general tab I believe) so as to try to make your settings stick as much as possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
so what I understand is it's better to keep mp-decision enabled with leankernel... right?

My brain must be elsewhere this morning because I do not understand what I should do! ;)

I can see that when mp-decision is off, both core will always stay on at the lower frequency when there is a very low cpu usage... but with mp-decision enabled, the second core will shutdown in this case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's a matter of taste, but I prefer the slight battery savings that come from having hot plug working (hot plug being enabling disabling of unneeded CPU cores) and thus when using kernel I have MP decision ENABLED and Frequency Lock ENABLED (so as to keep my custom CPU settings).

Cheers :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Hey guys,

Those of you like to have mpdecision disabled, what exactly does it do that affects your experience in a negative way? I personally don't mind it enabled but I don't generally tweak my kernel settings at run time, because they're more or less set to how I like them by default. ;)

Maybe I'll look at mpdecision and try to tweak it itself if the project is interesting enough...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
I've always disabled it b/c it's just another process or system file running in the background by controlling hotplugging, when the right governor/kernel is more than capable of controlling hotpluging without the use of the mpdecision file.

I know your governor doesn't necessarily control hotplugging without the file enabled, but that doesn't bother me.

Would it be possible to enable hotplugging within the governor itself, without using the file?

I switch between Lean Kernel and BMS (i.e. Trinity kernel) Kernel, using asswax governor, with mpdecision disabled, and hotplugging seems to work just fine; think he uses a tweaked auto hotplug driver. Also remember Ktoonz having hotpluggin built into his kernel, and you can have mpdecision disabled..... on the other hand, I may have no idea what I'm talking about. I just know a lot of ROMs have it straight out removed so that it will not "interfere" with the kernel, use more battery, etc. Also, don't want it interfering with my other kernel setting, be it the governor, governor settings or selected frequencies.

F.Y.I. here's the best description of MP-decision that I could find:

"The mpdecision file runs in our system as a vendor executable file and what it does is that it controls the governor for cpu, this file is very important as it defines performance of your cpu1, the file gets executed every time your screen goes off, hence cpu1 scripts are useless because the mpdecision file overwrites the cpu1 governor settings to userspace ondemand, userspace is the governor when cpu1 is online and ondemand when offline."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thalamus made an alternative auto-hotplug that works wonderfully if someone wants to ditch MP decision for good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Ah I have already tweaked my kernel to prevent the cpu1 governor behavior described above so you're good there. As for mpdecision itself, it actually does quite a bit more than just hotplugging cpus. It handles various cpu sleep modes, thermal tweaks, etc. I honestly think it does a pretty good job. On the other hand, there may be perceived performance improvement when disabled in my kernel since cpu hotplugging does add a little overhead. I don't think you'll see a huge difference in power efficiency whether it's disabled or enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpulford311:
Ok trying to download this kernel but when I click on stable it takes me to a page where there are multiple folders. I have at&t. Am I retarded because I didn't see which kernel I needed, none of them say at&t. Lol. Sorry
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Look for the exp folder and then for a file named lk_s3att_aosp_43-v7.1exp1.zip :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mpulford311:
Found it thanks.

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
SOC Temperature throttle. yes or no?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tingljjdehua:
sorry for my misbehaviour but I'm really looking forward to the next 7.2 release. but it seems everyone out there in the forum are putting their heads in android 4.3. anyway, can't wait to flash the new release!:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
F.Y.I. New version 7.2 is up. :)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Swiftks, you are too fast! ;)

v7.2 is up: https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog

I actually merged the entire cm-10.2 branch into this android 4.2 kernel, so if things are broken go back to v7.1 and report it here. I tested with the latest cm-10.1 nightly and everything seems to be working fine.

v7.2 *should* work on cm-10.2 unofficial builds as well but I haven't tested that personally. It does not have SELinux enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Was just about to say that the new experimental build is running smoother than ever, which it is BTW, but then I got a screen lockup when trying to wake; i.e. the same issue we were having a couple of builds ago.... Going to update to Slim v8.0 and give it one more go before I go back to v7.1

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Ah my fix got reverted when I merged in cm-10.2 source. Building exp2 now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
No go on cm10.2, got a black screen when unlocking just FYI
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I too got bad experience with 10.2, will wait until CM publish the couple of nightlies before giving this a try
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Looks good now with exp2.

I have a question regarding the temperature throttle option in trickster mod and your kernel. Is this option useful or needed when I overclock to the max frequency?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Since v7, whenever I reboot after installing Lean Kernel, I get "Android is upgrading" N number of times
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
Thanks for the update. Just flashed 7.2 on Slim 4.2.2 Build 8 but seeing all step voltages at 1150MHz in Trickster mod :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
it's always been like that for the voltage... you can easily change it after a flash. I do it all the time without any problem.

I'm running my device at 875mv for 192 and 384MHz... I add 25mv of each other step to reach 1175mv for 1512MHz. I don't changer other higher speed.

I think it's a good idea to put 1150mv for everything... not all devices are equal... some are using even lower voltage without any problem... but on mine, If I go below 875mv, I will eventually get some random reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
From what I've seen most phones seem to not like lower than 875mv for 192mhz and sometimes even 900mv for 384mhz. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
It is good to be not in the most phones range. 825@192 never had any issues. Will probably lower 25 more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's to note I'm very stringent about my undervolting/overclocking stability. When you use your phone as a work phone, you can't take the chance of it rebooting on you.

I myself prefer to stay on the stock voltage considering how very little undervolting saves me battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eggydrums:
Hey guys, is this compatible with Tmo?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Woody:
I'm using it on TMo with RootBox just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Unicornasaurus:
Tried flashing the stable 4.1 kernel on Hyperdrive RLS15..booted to a black screen.

Any way of getting it working? I really like Leankernel :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Am I the only one experiencing this? Even after rebooting the phone for 10+ times, I keep getting "Android is upgrading" prompt. Clean flash(Slim ROM 8.0), tried clearing the cache.

I experience this only after flashing Lean Kernel on Slim ROM, had the same problem on Slim ROM 7.0

Can anyone else confirm if other users are experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Think you're the only one.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I got that before with the stock cm kernel on my nexus s. It was annoying. Never really found why though.

Might be about zip aligning though. Or something similar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bytes2bits:
No issues here. I'm on LiquidSmooth. You sure you don't have an optimization app set to clear cache on a reboot (rom toolbox or something similar)? Just a wild guess. Probably not the problem. You can try searching Google for this problem in general. There are many mentions of this problem. Maybe it will head you in the right direction.

Also, if you're using Titanium Backup, just try uninstalling it as a test.

Take a look at this thread. It has some interesting general suggestions. Good luck.

http://xdaforums.com/showthread.php?t=2177032
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for your response. I have uninstalled apps like Titanium, Greenify which are system apps and may cause this issue.

What is interesting, if i flash another kernel after clean install, I dont face this issue. Maybe my phone does like the latest lean update.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I would check init.d script if you haven't already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Been using the kernel for a little bit and so far love it.. Just wanted to say thank you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Here's a test build for cm-10.2 (android 4.3): http://www.box.com/shared/jl52bgdbnn56j6q5apjp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ih8mydroid:
Boots up and runs great on the latest 8/9 10.2 unofficial build. Ill let it cycle a bit and see how it does but thus far its much smoother than stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
4.3 Up and running here also on Pwncakes 8/9 build.

Will report any issues.

Thanks Imo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeeahnick:
Hi,

Id like to try this kernel but i am a bit confused on which version i have to install. I am running rootbox 4.2.2.

Id like to try stable 7.1 but i see that 7.1 exp1 came out 2 hours later so is exp1 better then stable?

Also same thing with stable 7.2 i also see 7.2 exp2 that came after the stable?

Thanks for clearing it up for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
both are using the same code base... so one should be as good as the other.

exp has a few experimental feature (like down clock to 192MHz) that are not available in the stable release... but except for that, I really do not know what is the real difference. I've been using the exp for some time now... got a few problem with the 192MHz clock speed (phone was freezing when going to deep sleep)... but this was fixed fast by the dev.

even the exp is really stable.

7.2 exp has a second version because the first one had a bug with the 192MHz clock speed... exp2 fixed this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Woody:
[MENTION=4201689]yeeahnick[/MENTION]

I am using RB 4.2Stable and using this 7.2exp2 just fine. Had some RR's in the beginning but that was mainly my fault and too low of an undervolt on the lower freqs. Pretty solid build(s).

If you want some good ideal settings, see these from [MENTION=3812527]Swiftks[/MENTION]. I had to tweak some things on my end (i.e. different voltages on some lower clocks, higher clock on another), but pretty solid settings he's found there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
No just 4.2.2 aosp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boss Daddy:
Works with AOSP and AOKP 4.2.2 ROMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rapproduca:
Thanks but I figured out that my usb cord is just janky. I used a different one and no wakelock :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Hold up, it says d2vzw on the one I downloaded... Can I still flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No, get d2att.

Quick question: Got v2.9 installed right now, that's the last 3.0 kernel right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radekg7:
Imoseyon is this kernel support sgs3 international??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmendc:
I looked through but can't find the answer... I'm running CarbonROM with the last Linux base (3.0)..which file should I flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
2.9 I believe, but I basically asked the same question as you. Make sure to get the right version for your phone (d2att/tmo).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmendc:
Done thank you! I flashed the 3/3 stable release i believe. Working great!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
3/3 stable is v2.8 if I'm not mistaken.

Changelog for v2.9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] karmendc:
Nice catch! Fixed now, thank you for your help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
v5.3.4 is up!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks man. Do you ever sleep?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
Awesome. 5.3 has been working great for me on the latest CM nightly :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
What is the difference between 5.3.4 and 5.3.4exp1? I tend to always be on the edge and naturally prefer exp1. But those were uploaded almost at the same time, so I'm wondering. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
I stand corrected lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
If only every dev made morfic colors optional. With just a switch flip/script toggle. Because those are matter of preference and look good in daylight but too harsh during night time reading when you actually need some red hues on your screen.

---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------

Just switched from SetCPU to Trickster Mod to find out that kernel specific features like ffc can be toggled by the simple switch in the Specific tab of Trickster MOD. No need to run script from terminal any more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
OMG thank you so very much! My flashaholic needs are fulfilled! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
Sorry I still need to update my change logs for exp builds. Here's what it looks like currently (changes on top of my stable build):

imoseyon:c324b61: acpuclock: add the missing slot

faux123:d2c1dba: sound control: update control offsets for MSM8960 soc

faux123:435bd14: Sound Control: Sound control for WCD93xx codec

imoseyon:e118b95: msm: display: overclock mdp

Vinay Roy:983ca3c: msm: kgsl: Calculate busy interval considering GPU freq as float

imoseyon:7da5020: lk.ramdisk: keep 384mhz as default low

imoseyon:c235d1e: acpuclock-8960: add 192mhz slot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z34370z:
Omg new kernel (Faints)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I'll just add that the voltages used on those settings are extremely low and many phones, like yours, just can't get that low without problems. I would suggest upping everything below 800MHz by 50mV, and a bit more with a finicky phone.. The upper values can be upped by 25mV if you have any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
for my phone, I start at 900mv for 192 and 384MHz... and I add 25mv for each step to reach 1200mv for 1512MHz.

If I go below that, I'm getting some random reboots...

So every device are different...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeeahnick:
download links are down =(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
you can get the latest 7.2exp2 for the d2att here : http://goo.gl/DRR15O
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
The website was changed!

anyone tried lk_s3att_aosp_mr2-v8.0rc1.zip?

Edit: nevermind aosp_mr2 = Android 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Just like to report that I am seeing some nasty screen tearing on the 8.0 Rc1 build. I'm running the 8/14 CM10.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Confirmed. Just flashed last 10.2 official nightly and there was a lot of screen tearing when scrolling fast. Reflashed the rom with stock kernel and problem was gone.

---------- Post added at 04:00 PM ---------- Previous post was at 03:53 PM ----------

website was changed to what? New url? Old one still isn't accessible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Don't use your bookmark, use the links in the OP

http://androtransfer.com/?developer=imoseyon&folder=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmh033089:
Will this work on d2cri the cricket verison of the sgs3 and rsl15 rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I don't know, but probably not. And if it doesn't and you flash it... you own a $600 brick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] halodos:
installed the MR2 8/14 update for the d2_spr. runs great now, but had some tearing at the beginning. disabling hardware overlays fixed the tearing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
When trying to download the kernel, I'm getting the 10 seconds countdown in an infinite loop... After 10 seconds, it starts over again.

I'm getting this with both Google Chrome and stock browser on the latest CyanogenMod nightly

... I just tried it again and it works fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Rc3 is up. Go get it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
So far so good. No screen tearing on this one. Will report if notice any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I've had lk 7.2 running perfectly with carbon nightlys except for today's release.. Lots of FCs.. Should I be using another version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Is carbon still on 4.2.2 branch? Because this kernel is for 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
It does have 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Yeah for the past 7 days
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Woody:
This kernel is for both 4.2 (7.0,7.1,7.2) and 4.3 (RC1,2,3), you just have to download the correct one.

[MENTION=4334272]waiters[/MENTION] Have you tried the usual fixes?

Reflash the kernel again

Reflash the ROM with its kernel and boot up and check for FCs, then flash LK

Recovery>Fix Permissions

Aligning the stars on Thursday might also help

FWIW, I am still and staying on a 4.2 ROM until some of the 4.3 bugginess gets cleaned. ROMs are great, it is just that not all apps are optimized for 4.3 yet and I have no desire to go through the PITA that was the ICS>JB app conversion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Rc3 boots fine with newest nightly of carbon :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Lean Kernel v8.0(Android 4.3) stable is out, go get it guys!! Here we go Android 4.3 :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Just installed and running.. So far so Good on beta3 of slim!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
If I helped, please hit the thanks button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Got into a boot loop with 8.0exp1 and cm-10.2-20130826-nightly. Stable works good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
Same here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Imoseyon:
sorry about the exp build guys, exp2 should fix the bootloop problem: http://androtransfer.com/?developer=imoseyon&folder=d2att/exp

and here's the changelog for v8.0 (android 4.3 only): https://github.com/imoseyon/leanKernel-d2vzw/wiki/AOSP-ChangeLog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Been running the new stable build all day on Slim beta 3, no problems.

Just switched to the new experimental build, and screen wouldn't come on after going into deep sleep... Same kind of thing that was going on a few builds back for 4.2.2

Sure it will get worked, as 4.3 is still pretty new. Just wanted to report my findings.

Glad your back Imoseyon, hope you had a good, and well deserved, vacation.