yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Is hispeed_freq what the CPU scales to when first touched, and then ramps up or down as needed? So by setting to 810 instead of the default max frequency value of 1512, the thinking is that it may not need to scale as high and therefore save juice and be better on battery?

Just trying to understand.

Great kernel GidX. :):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
hispeed_freq is the speed it'll ramp up to once go_hispeed_load is reached. But yes, setting it to 810 instead of 1512 would prevent it from going to 1512 all the time instantly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
Any update for 3.0? Would love those enhancements you are making for 3.4.

Sent from my AT&T Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
So.. any chance of a TW kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I'll get to that shortly :)

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Not at the moment, sorry.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ragz:
Using these settings is most definitely working for me, battery life is best ever on Deviant x.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Party hard. Still on latest CM10.1 based off 3.0. It just feels so smooth I'm scared of going back to 3.4 :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Do you build ROM? How come you are still on 3.0 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
using an older version and not updating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That. Using CM10.1 from March 17th. It just works, I used to be on the latest nightlies but when at the start of April applications just didn't work because of the bug that was introduced (Play Store "crashing" and such) I just rolled back to that version. I'm gonna ride it until there's something really worth updating. 8)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
FYI morfic has a trinity kernel for stock ROMs in the tmo section that I've used which should be pretty similar to this kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
Ahhhhhh I can't wait. I need me an update! Thanks for all the work man.

Sent from my AT&T Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznxprd:
Using these settings on the newest update makes my phone so smooth!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doritos93:
How's this kernel compare to the kernel bundled in Task650's rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Try and find out yourself
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doritos93:
Ok!

Everyone's a hero
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
You mad bro? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doritos93:
No, I said I'd try it out. It's good so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
Can't wait for the next 3.0 release. The 3/17 cm10.1 build had been really stable for me. Haven't been convinced to go back to 3.4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
3.4 rebooting my phone with task 4/17 when use video cam and Google hangout
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
I was wondering the same thing in this post from your other thread, http://xdaforums.com/showpost.php?p=40484730&postcount=367

Also, I've been itching to try cm10.1 and so I downloaded the 4/17 build so I could use this kernel, I've got a few hours into feeling it out and so far it is damn smooth. My first venture into the 3.4 realm, I'm curious to find out what battery life will be like.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wujiku:
try the new 4/19 builds.. fixes display issues and other glitches
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Built one yesterday, but didn't have a rom with the changes to test. I'll have one out shortly with the display updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y Build 2013-04-20 - http://www.droidhype.com/kernel/34/

This was tested against CM nightly build 4/20 and has been solid so far. It was also tested against the Carbon 4/20 build, but display distortion was evident.

- Many CM/CAF updates

- Linux 3.4.41

- Supports new display driver changes in CM and CM based roms (nightlies after 4/19). If you flash on a rom that does not have the updated display drivers, you will boot to a black screen. If your rom developer does not have an update for these changes, flash the 4/15 release until you get an update.

- Added FIFO scheduler

- Tweaked ROW scheduler
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
This new build is a treat. So smooth and amazing battery life. This kernel is awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Working good with task aokp latest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Which tool i should use to change governor settings on the latest build?

TricksterMOD only shows 2 governor(ondemand and performance). I am using TASK AOKP

Edit: Found it, using TricksterMOD for the first time.

Quick Question: Any fix for Asswax? Does not appear
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Asswax gone on 3.4. Too much of a pain in the....

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update. Stable with latest task aokp rom but only with random screen flickering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Too much of a pain in the asswax
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Xone update coming soon so here I come build 4/20 lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ragz:
Same here BMS down loaded, and waiting for xone, anticipating new level of smoothness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
Anyone running the new slim bean with bms? I keep getting black screen even with the old versions.

Sent from my AT&T Samsung Galaxy S III

---------- Post added at 12:07 PM ---------- Previous post was at 12:06 PM ----------

Running latest slim bean and trying to use 3.4 kernels

Sent from my AT&T Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
4/20 release should work fine with slim build 4.1 if u didn't update to 4.1 build it won't work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
Yeah I'm on 4.1 and doesn't work :(

Sent from my AT&T Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toyanucci:
Im on slimbean rom 4.1 too, and the latest BMS kernel works, until I plug it into my computer. As I plug in USB, my att S3 reboots :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ragz:
4/20 BMS is working great with latest (4/21) Deviant X. Great work and Thank- you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Currently an issue with USB. Phone will not boot if connected to a computer, also you will not be able to use the phone to transfer files, will be updated to fix in time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Phone wont boot while on the charger as well. Im sure Gideon is checking it out.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Hmmnn...Im on slim 4.1 with the 4.20 build of BMS. Seems fine for me so far. Haven't plugged into my laptop yet but will see...

Any recommendations on governors for this latest 3.4 build? I was using asswax on the old school builds and it worked great. Anything comparable with good battery life and performance? I am using conservative now and it is working well. Just curious what others are using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Interactive/row. Set hispeed_freq to 810000 mhz.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
I have the same issue, with "[ROM][DEVIANT][d2att][4.2.2] Deviant Xone - 4|21|13" but works fine as long as its not plugged in, My battery will not last that long :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Build with usb/pc/reboot fix will be up shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Told ya gideon was on it.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Would have been quicker, but Sundays + 2 kids = disaster
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
:) thanks for your help

---------- Post added at 11:34 PM ---------- Previous post was at 11:32 PM ----------

That's OK as long as There will be one up soon, for now wall charger is doing its job :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
I know how ya feel Ed.

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Screen issues are back... are they part of the kernel or the rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.4.y Build 2013-04-22 - http://www.droidhype.com/kernel/34/

- Haptic feedback adjustment now available. In CM, settings->advanced->haptic.

- Fixed USB to PC and reboot while charging issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Axis_Drummer:
Lol

Samsung Galaxy SIII

Booped by BMS

Nice :thumbup::cool::thumbup:

Sent from yours truly..

ΧΔΑ Fraternity's Rush Chairman
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hmm I don't know why but even after a week of charge cycles I see poor battery life with this kernel paired with Task's AOKP. I get around 2 hours of screen time while I get 3-3.5 on Lean and KT747.

Do I need to adjust something in the settings? I'm just running stock kernel settings right now.

Another issue I have is severe battery drain at random points during the day, but they can be easily solved by a quick reboot. When I flash to a different kernel this issue no longer persists. Anyone seen this happen to them?

Hoping to get these issues fixed as this kernel has some great performance!

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
Kernel working good, but flickers with gosms, and or the keyboard sometimes :) mostly when holding a key to have the second option of that key
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
man I sound foolish but bms kernel and faux sound is separated if so im looking for faux sound
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
I removed swiftkey and problem seems solved. Anyways didnt see keyboard flicker since :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Fauxsound patch is implemented into the kernel. You have to get the app from the playstore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
What Steve said ^^^
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
awesome thanks guys i was getting confused on whats what lol.. looking at it now in the play store..seems like its a good match to the bms kernel ill give it a shot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I was getting bad batt life with his rom and this kernel as well. Currently using cm nightlies and it's some of the best I've ever seen. Avg 0.6% drain per hour overnight while idle, so just about 6% batt loss every 12 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
On the newest deviant battery life is awesome. Same goes for liquid nightly. Awesome battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -oH-mr_rogers:
help

i flashed deviant xone and BMS 4-22 kernel and my phone boots to the BMS boot animation then goes black screen, but its on.

and when i try and go back to recovery mode it just keeps booting up and skipping past going into recovery..

can anyone help me with this please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Wouldn't let me get deep sleep. Anyone know what this is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
You might need to reflash your recovery. I had the same issue not too long ago where my sdcard0 was corrupted somehow. It prevent TWRP from loading correctly so I was in a recovery bootloop. Ended up using odin to flash the stock recovery and then twrp again to clear it up.

That's a bluetooth wakelock if I recall correctly. What rom are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] -oH-mr_rogers:
im kind of new to gs3 is there a forum that will give me a step by step or can you tell me how to flash stock recovery then twrp again

(very much so donation will come your way for the step by step) lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Oh that makes sense...it was enables but wasn't checked in my quick settings. Slim 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
rmead01 got it in his steps.

No need for donations, this is a hobby and it should stay that way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Just want to show off what unicorn magic and sprinkles can do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] houstonsveryown:
Tried 3.4 on Paranoidkangdroid. nothing but a black screen. Not sure why 3.0 work just as fine back then when the ROM was on 3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
The new kernels have pushed display commits that won't work until pkd has been updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] houstonsveryown:
ooh. I see. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
I just installed newest liquid nightly and this kernel...data is moving fine but the bars are grayed out. Any thoughts? I figured it makes more sense for this to be kernel related than rom, but I'm probably wrong. :)

Sent from Bananaphone v2.0 (Final)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Sync is either off or something else :p go to settings - data usage - menu - auto sync
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobstradamus:
When I click to download the newest d2att/d2tmo version, the file downloaded is labeled d2spr. Just want to make sure this is correct before flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
You're tapping the link below it. Zoom in and tap :)

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobstradamus:
I even retried to make sure I didn't do that before posting and turns out my thumbs are bigger than I thought. Thanks for fixing stupid with grace.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
I'll edit the html and add a line break between links. That should help.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Ah, that's smart. I have sync on a timer. Thanks for the reply!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Grey bars don't mean anything about signal other than you don't have a connection to googles sync servers. Otherwise blue and grey are exactly the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TomMelee:
Ok, I thought it meant that the device wasn't registered on the network. For example, when I accidentally wiped the IMEI on my captivate (ok, and my s3), I had full signal but gray bars and data wasn't moving. I've also experimented with APN's and had it show signal but gray bars and no data...and like now, I'm NOT syncing, but the bars are blue. It doesn't really matter, I just wondered.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Quick question: how to disable the cm nightly performance app, can't find it in titanium backup. Using trickster mod as suggested in this thread. Don't want the two application to fight and kill the battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Go to Settings -> Performance and untick Set at boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
The best way is to go into your superuser app and deny performance app from gaining root. That way you know for sure it's not doing anything to your CPU settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
It does not appear in the log, using the latest nightly 4/23
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
If it's not in the log then it probably doesn't have root access which means it can't change anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Are you guys referring to Settings->Performance setting in CM based roms? Cause I believe it appears as something else in superuser logs. Not too sure what though, I don't use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
I'm running CM and I've never touched it. Don't have any issues so i'm not sure. But if it was trying to access root and change things there would be a notification regardless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes I believe there is, but it's referenced as something else, not performance. I just don't remember what it is and I can't check now. Doh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
under system it says "Performance"

When going into these settings since it's a root function built into the phone there is no request or log bad with superuser. But it won't do anything unless you provoke it or have it running on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
For those who were asking about faux sound control its now built into trickster mod no need for the separate app anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
If you decide to purchase the donate version of trickster mod. In that case, I'll just support faux.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I know the menu is called Performance and is located in the System section of the settings, but I meant the reference in the superuser logs. Can't deny "Performance" from superuser because this entry wouldn't appear. Gideon was suggesting to block it from root rights.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Opps sorry I always buy donate versions still have fauxs apps aswell so I supported both just nice to have it all In one app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
But if it isn't being triggered there is no need to block it. It will never do anything unless you tell it to
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Agreed. I wasn't the one suggesting that, Gideon was. I suggested just to untick the run at boot option. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Unchecking that can't hurt :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Asswax gov is making a come back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Gid this new build is gonna be a game changer!

ATT SGS3 Xoned out on BMS baby!

4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Habs69M:
Cant wait :)

Sent from my samsung t999v
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
CM has a new commit that fixes flickering. I guess I'm releasing early again.

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
Oh the FLICKERINGGG!! The HORROR!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Which version to use with Liquid Smooth?? :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Go to Settings>About Phone and check your kernel version. If it says 3.0.xx download the 3.0 version. If it says 3.4.xx download the 3.4 version. Sorry I don't know right off (I don't run LS) but that will give you your answer. :)

Edit: I don't believe LS has been updated with the latest display commits, so you'll want to use the 4/15 build, not the most recent. Someone please correct me if I am wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nrod0784:
Just trying out this kernel for the first time. Im looking for best battery/perfomance recommendations on this kernel with cm10.1 nightlys. Any advice is much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
I just flashed this, and now I think the Play Store is bork.

Whenever I open it, it just closes right back out again.

I've tried:

-Clearing cache

-Rebooting phone

-Clearing data

-Stopping the app

Nothing's worked! Halp, again? :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 850T5m:
Shouldn't have anything to do with the kernel...try reflashing gapps

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Interactive/row
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Also go into the interactive settings and change the high speed freq to 810000
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
If the above suggestion doesn't do the trick, then try removing and re-adding your Google account. I have a complete walk-through on how to do this on my thread here:

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

It includes wiping cache from the Google apk's also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
It's likely not kernel related, but try re-flashing gapps or re-adding your user as suggested by the other folks here.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Yep, reflashed the gapps and that was the ticket!

Great kernel, by the way, loving the battery life so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.0 and 3.4 builds coming later tonight.

Sent from my SCH-I535
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nrod0784:
Thanks guys. No stutters thus far and idling battery is great thus far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
3.0.y Build 2013-04-27 - http://www.droidhype.com/kernel/30

- Updated to Linux 3.0.75
- Updated to Linux 3.0.74
- Updated to Linux 3.0.73
- Updated to Linux 3.0.72
- Updated to Linux 3.0.71
- Added fixed asswax scheduler (credit DecimalMan)
- Added fifo scheduler
- Fixed pll8_clk
- Tweaked row scheduler

3.4.y Build 2013-04-27 - http://www.droidhype.com/kernel/34

- Merged latest CM updates (screen flicker should be fixed)
- Added fixed asswax governor. Interaction bits have been removed as suggested. (credit DecimalMan).
- auto_hotplug.c: helped decrease lag with late resume (on screen wake) (credit morfic and franciscofranco)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antharr:
Still showing 4-22 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GideonX:
Odd, I'm seeing the update on my end on the page. Are you on your phone or PC?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antharr:
I am on my phone ATM. I will check on PC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:


Shows up fine for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] antharr:
My bad. Link redirects to correct build on PC and anything other than Chrome on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Is this not booting up for anybody? Just downloaded twice and flashed twice. Both times it boots up but the screen remains off. Can't see anything can't unlock the screen.

Just re-flashed 4-22 and I'm back to normal again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Worked fine for me. You could always try a good ole clear cache, clear delvik, and fix permissions. I usually do that anyway when updating a kernel.

Any suggestions from anyone on choosing my scheduler? Ive been using SIO and it seems to be good. Just curious maybe what others suggest.

Thanks for bringing back the asswax! I cant lie. I mostly like it just the name :p Performance seems good though with it. Also good battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ragz:
04/27 is working fine with deviant zone beta 2, as always I love this kernel, smooth and crisp. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Give Fifo a shot. simpler then noop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Yup, tried all that already.

cache, dalvik, permissions. I do all of that, except permissions, after each new kernel as well.

I'll try downloading to my computer first, then copy over and flash. I wonder if maybe it's just that the phone didn't download the entire package properly.