yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peecs121:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

I know the op says to not wipe. Just wondering if you would get better results with the wipe cache, dalvik and fix permission for best results?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Wiping doesn't make a difference except slow your boot up when flashing a kernel. Don't let anyone tell you that it makes a difference because it's total BS ;)

However, this is assuming you have no other issues with your rom. If you are having, for example, FCs or whatnot then you would probably benefit from a wipe or permission fix before doing any kind of kernel tinkering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Not sure but I always wipe before and after flashing kernel. I dont really ever fix permissions though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thehavock18:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Also noticed that the governor needs to be ondemand
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
How so? What do you mean by "needs" to be?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peecs121:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

I'm running Interactive with Row and it's running super smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
I was using trickster mod. But installed setcpu and tried that as well as the performance app built into the rom. None of them shows 192. They show the overclocking and all the govenors so irdk. Thanks for taking the time to help btw!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [KERNEL][JB42][AOSP] ¤ BMS ¤ d2att [2013-03-04]

Reflash maybe cuz I see 192 using trickster mod

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rob116:
Perfect, thanks, I'll give it a shot. Thought I'd seen something like that on one of the boards, but couldn't find it. Much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] illmatic24:
This kernel is running beautifully with pwncakes latest CM 10.2 build. thank you :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Anyone running this bad boy with Slim Bean build 8? flashed the kernel yesterday and might battery drained completely overnight. No rogue apps as far as I know..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Running just fine. Give it a couple days to settle down before passing judgment though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psp9000333:
running same rom by pwncakes. great kernel!

---------- Post added at 10:11 PM ---------- Previous post was at 09:52 PM ----------

also, how does trinity colors work and how do you enable fast charge?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
You can adjust color temps within your rom settings if it's cm based or open terminal emulator and type su and then 'setcolor'. My script can enable or disable trinity colors.

Fast charge can be triggered via Trickstermod or similar kernel app. I can add a script if enough people prefer that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psp9000333:
why is it when i overclock my device to 1.8 GHz it always reboots even if im not doing anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Sounds like your phone can't handle it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rob116:
Lol, you're a really nice guy Gideon. Some people around here would respond very differently to a question like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Nice guys are nice. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psp9000333:
nvm, its just the app im using to overclock is causing the reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psp9000333:
im getting bad battery life even without overclock and im consistently getting reboots and shutdowns. switching back to stock CyanogenMod kernel. too bad at this time this is the only kernel for the AOSP 4.3 version of the d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
So what app are you using to control the kernel? I hope it isn't the built in performance settings in CM...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psp9000333:
i was using the app provided by rom toolbox pro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Never used that one, always suggested folks use trickstermod.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Build 2013-08-14 - http://www.droidhype.com/kernel/34/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Build 2013-08-15 - www.droidhype.com/kernel/34
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Camera not working with pwn rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
What's the build date on that rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Gideon, when I flash your build for today, my phone has no signal & when I check my IMEI, it says unknown. As soon as I refresh the ROM & stock kernel, my IMEI shows up & it grabs a signal like normal. Any idea? I'm also running PwnCakes latest ROM that was posted today. I believe he's calling it Quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Happened to another user today, they had to reflash rom and BMS and it came back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Ok. I'll give it a try. Thanks.

Sent from my Galaxy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
8.14.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Just built late last night
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Hang tight, rebuilding another version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Folks with IMEI/baseband weirdness, re-download the zip and re-flash today's build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew_han:
What does removing thermald do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Let your phone burn. :p

But on a more serious note, remove the frequency throttle (stepping down of CPU frequency) that happens when CPU heat gets a bit too high.

I am not sure, but I believe the SOC still has a thermal shutdown but quite a bit farther from the default. Correct me if I'm wrong Gid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Correct, there's s hardware limit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
https://lwn.net/Articles/563687/

Hello exfat.

Compiled, anyone want to try and let me know if it works?

d2att/d2tmo 2013-08-17 - http://goo.gl/gliFrX
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
in layman's terms, what does this mean and for what version, 4.2.2 or 3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I only build 4.3 kernels now.

Here's exfat on wikipedia:

http://en.wikipedia.org/wiki/ExFAT

The 4GB or larger file size support is the major advantage over fat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
thank you sir
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Love your work... when are you getting an S4? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Lol, this s3 is still rocking ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Never... Nexus 5 or bust!!! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Played with an S4. Unimpressed. Swear my 3 on deTmobilized ROM was faster. Won't even compare on 4.3! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
Just flashed this over PA 3.97 which was built on the 18th and flashed the 8-15 3.4 but i am experiencing alot of screen lag and choppyness. is there any adjustments in particular i should make or could this be due to the PA build being slightly more recent?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Not entirely sure, I've noticed PA users are still getting screen issues. Only time I've seen that is when some of the newer cm commits weren't merged on the rom side.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
hmm could be theres alot of changes going on with it trying to get everything on 4.3. BMS has been great so far though, really great battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
I've had a couple weird reboots, and this morning I woke up (I was charging my phone) and it wouldn't wake up, though there was a blinking green light (which indicates a notification for me).

What do I need to do to figure out what could be causing it? I'm running slimbean 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Running BMS as is? Or did you change anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
If you can still receive notifications, but the device doesn't wake up, it ususally sounds like an issue with voltage... Might need to bump them up a bit to get it to stabilise?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I thought exfat was a lot slower?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Possible, don't have the means to test that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ant_129:
I just had to come over and say thanks. I'm getting the best battery life ever thanks to this kernel. I'm using it with CM10.2. It was draining so fast but your kernel fixed everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm considering switching over to this kernel from Bionic Sheep...It looks really solid. Do you guys tweak it or leave it as is? Running Quantum 1.18
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Don't just consider man, FLASH IT RIGHT NOW! ;) One of my favorite kernels from good ole s3 days! How you doing gid?

Sent from my Samsung Galaxy S4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I leave it as is with ondemand but change the low freq to 189. Absolutely amazing performance and battery life for my usage. 4.3 is no joke compared to 4.2.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Gid what cycle is followed for updating the 4.3 kernel? long time no updates :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ant_129:
Well I found a bug that I can't live with. I get no audio on the left channel on certain apps. It doesn't affect them all the time, it seems random. Earlier in the thread it was suggested that it is a ROM bug but I have no audio problems with the stock CM10.1 kernel. I have flashed it between the two a few times to verify. Its a shame too, such good battery life.

Edit: It must be something with my device, I tried leankernel and have the same issue. I don't know whats going on. I am on CM 10.1.0-RC5-d2att and have also tried CM 10.1.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Doing fab, jumped to the S4 I see ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I should have another one out this week. I pushed a test build out last week, check the previous posts if you want to try it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Flash the latest CM10.1 nightly. I'm almost certain the RC and stables you flashed are missing a few things. Use BMS 7/30 release if you plan to stay on CM10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't see why you're still running CM10.1.0 RC5. I suggest you either jump to the latest CM10.1 nightly or CM10.2 nightly and then report back. I have no such issues, both music or in games and I'm using latest BMS for CM10.1. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Definitely...I always lower the lowest freq to the lowest it can go and sometimes even the higher frequency to 1.24 or 1.35 :laugh:

I did not default to ondemand/row, I checked the init.qcom.post_boot.sh file and it is writing interactive/cfq so I renamed it to init.qcom.post_boot.sh.bak and reflashed the kernel, now when I open trickster it's ondemand/row. Is there any harm in this?

Looking forward to it man! I'm gonna flash the latest test release, I always like the most updated kernels cause the CM10.2 source is being updated a mile a minute.

Is this it?

Still, it's from 8/17 - In the past 10 days I'm sure CM code was updated quite a bit! Not rushing you at all man, I'm sure I'll be happy with this build :cool:

Would it be the ROM that needs editing to add a fast charge toggle to the quick settings tiles? Or is that something you can add with your kernel? My guess is ROM, but it doesn't hurt to ask.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Cm kernel actually has been pretty quiet. So you really aren't missing much. The rom is another story...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I actually just checked myself :)

You're absolutely correct sir. I spoke too soon!

Also this question was directed at you because I am not sure how important the file is:

init.qcom.post_boot.sh is the clear culprit here for me because my ROM flash pushes it's own file there. So my question is - is adding a .bak extension to that script sufficient to get rid of the issue? It concerns me that a new script was not generated once I rebooted, it's still just a .bak script.

I'm positive the the ROM I'm using changed the init.qcom.post_boot.sh file to include the settings for their kernel, ROM is Quantum 1.19. Opening the RAR file of the ROM and browsing to /system/etc/init.com.post_boot.sh and opening the file shows this:

Line 30-36

case "$target" in
"msm7201a_ffa" | "msm7201a_surf" | "msm7627_ffa" | "msm7627_6x" | "msm7627a" | "msm7627_surf" | \
"qsd8250_surf" | "qsd8250_ffa" | "msm7630_surf" | "msm7630_1x" | "msm7630_fusion" | "qsd8650a_st1x")
[B]echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor[/B]
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
;;
esac

so it should default to ondemand right?

Scroll down a bit more and this is what I find;

The first 2 lines are 57 and 58, I removed some filler in between to keep this post as short as possible.

The rest, where it has #echo (not applied obviously because of the #) is from lines 72-77 and the following lines without the hashtags are 78 & 79

case "$target" in
"msm8660")
#echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
#echo 50000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
#echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
#echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
#echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
[B] echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "interactive" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor[/B]

It seems the

case "$target" in
"msmXXXXXXX")

Plays some kind of part in how it sets the kernel governer and scheduler...but I dunno man I'm a noob with this stuff.

This isn't the only place in my script where the OnDemand for scaling governer is hashtag'ed, I just don't want to bulk up this post too much.

SO, without further ado, here's my actual question:

This is the file that my ROM installs when flashed, is there any damage in renaming it to .sh.bak and ultimately just not having a post_boot.sh script in the directory? Should I edit it instead of (basically) deleting it? This is all very confusing to me :)

Maybe if you could upload your own BMS init.qcom.post_boot.sh script for me to look over/use that would probably solve all my woes. For now I'm running without that post_boot script, and all seems to be going just fine...but just getting rid of a system file seems like it could be risky.

Hope this isn't too convoluted, I would really appreciate some help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
The post boot file satisfies a bunch of devices. For our S3s, you are looking for the 8960. Check under there :)

Btw, a # before a line means it's commented out so it won't be considered. I would really just edit the file instead of renaming it. Or use an app to adjust your settings on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Yeah, I know the # comments it out, that's what I was concerned about. I'll just edit it under the 8960 section, cause I didn't know which was meant for our device. Thanks!

So how about this;

case "$target" in
"msm8660" | "msm8960" | "msm8974")
start mpdecision
;;

Do we want mpdecision? Using ondemand I had it turned off with Trickster cause I didn't want it to mess with my frequency lock. What's your take on this?

I'm confused as to why I have to edit this file :( Cause I want trickster to be the only thing that changes these settings on boot.

Could you maybe upload yours that's already set up to work with your ROM? I'm commenting out all the interactive stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
mpdecision has already been disabled in BMS, it uses a modified auto hotplug driver by thalamus.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
What polobunny said, no need to worry about mpdecision, disabled from the get go.

Tell you the truth, I don't edit anything in my post boot file. Trickstermod does the work for me after boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hi Gid,

We have 10.1.3 RC1 out, so can we have the last update for 10.1 based on RC1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Grab the 7/30 release. Not much changed on the 4.2.2 branch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ameanl:
Does BMS do Touchwiz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ant_129:
Thanks for your help guys. The latest RC for CM10.1 fixed my issue. Just curious why the CM stock kernel has such a huge battery drain. It would last 8 hours tops for me with light use and barely any apps installed. Whatever magic you do Gid solves this issue. 6 hours in today and have only dropped 25%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
CM10.1.3 RC1? It has an OTA update bug, BMS fixes nothing about that so it's bound to re-happen again.

A commit has been out to fix this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ant_129:
Which issue? I was referring to the CM10.1.3 RC1 fixing the audio bug that I had when used with a custom kernel. You guys had suggested flashing the latest nightly but I need a stable ROM. I got really excited yesterday when I saw that there was a new release candidate. BMS greatly improves my battery life from the kernel CM uses. I have noticed the poor battery life immediately after flashing CM and noticed the audio bug immediately after flashing a custom kernel. I am confused at what is bound to re-happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Lost me know this one. What are we talking about again? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's a bug currently with CM10.1.3 RC1 that has the OTA updater looping over and over and draining your battery. When I recommended the nightly (and a specific one at that), I recommended full knowingly that it was stable, I wouldn't recommend something I haven't tested or know extensively about. If you check my signature, you'll see I'm still running this exact nightly... and not the RC1. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ant_129:
Thanks for the info. Does that manifest itself in the google services? My phone lasted 12 hours with this Kernel but for 10 hours and 45 minutes google services had kept my phone awake. Still pretty darn impressive that with this kernel I can get that battery life with that long of a wakelock. I can't wait to see what it can do once the OTA updater is fixed. Also I was and still am unable to locate the nightly you had suggested. I've only seen 10.2 nightlies on get.cm.

CM10.1.3 RC 1 has a date added of 2013-08-28 16:14:16. With my limited knowledge of how CM stables are built and released I assumed that the cm-10.1-20130813-NIGHTLY-d2att would be part of the RC1.

Edit:

Found all builds of CM here.

http://goo.im/devs/cm/d2att/nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Your knowledge isn't completely off, but since it's an ever going update, CM gets old bugs fixed and new ones included. Hence why sometimes a nightly might fare super nice because most of the killer bugs are ironed out but a RC or even a stable have one lingering bug. It's ironic. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The last stable release was 10.1.2 which I will flash today with BMS(of course)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ant_129:
I tried that with BMS and had an audio glitch that allowed only one channel of audio to work. Maybe you will have better luck than me. I listen to podcasts daily and couldn't live with that bug and without BMS my battery would be dead in 8 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the heads-up, think Gid mentioned that 4.2.2 kernel is updated and will work even with 10.1.3. So thought it will work with 10.1.2

Will avoid falshing BMS over 10.1.2 until Gid release the fix.

Thanks, you saved restoring the whole ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
Uhm. I flashed this on probam and I lost service and the APNs dissapeared and couldn't save any new ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Reflash your rom, gapps, then BMS. It'll all come back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
The issue is that BMS is updated with the latest commits from cm, korg, and caf. So if a rc or stable rom is behind on new things, you end up with oddities like that audio glitch, screen tearing, etc.

I've always recommended nightly builds to flash. The RC and stables end up being "stale" very quickly. I also can't satisfy everyone since it'll be way too hard to accommodate all roms out there. I hope that makes sense :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
I followed those steps and the results were the same. No other kernels have this result.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yes. There is definitely other kernels that will give that same result if not flashed at the same time as the ROM & the Gapps. Kt's kernel does the same thing. You have to flash the ROM, Gapps, & kernel all at the same time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
Sorry giddeon and Robbie. I didn't realize that there was no reboot in between the flashes. Thank you both. My apologies for not understanding :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Didn't mean to come off sounding like a **** if I did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
No worries :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Smash2Bash:
No problem I'm cool :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I actually just flashed the newest version of DKP last night & I did not have that problem where I was having it before. Maybe it has been worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Is there a way to change the haptic vibration?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's under advanced settings in your rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
Never once had an issue with this kernel on any build to date.

Sent from my SAMSUNG-SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
The kernel seems to by having v sync issues. Low frames when scrolling up and down a page. Went back to an older version and all is well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
When was your rom built?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Android 4.3 Build 2013-09-06 - http://www.droidhype.com/kernel/34/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
OMG! An update! Woohoo!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Anyone run SIOPLUS Scheduler yet? Gonna try it out anyway but curious if anyone has any opinions on it yet.

Thanks for the update!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hkjr:
Nice work!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Using it with newly tweaked interactive. Not too shabby.