yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tacotino:
For all the cm users!!!

http://get.cm/?device=skyrocket&type=RC

Also I'm getting great battery life and speed!!! Thanks instigator

Everyone that is having cam issues try this...

cmw

Wipe cache

Wipe d-balls cache

Storage and mounts

And wipe cache there 3x... flash kernel the wipe cache one last time

That should work

Cm9

instigator kernel!!! OC/UV

custom ballz
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kuraijay:
still no luck D:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Yeah, I'm not doing all that wiping, it's usually not necessary. My camera worked fine in at least 2.8, and I'm pretty sure 3.2, now with 3.3 it doesn't work. I'll try going down and see if I can figure out when it broke. I am on 7/04 nightly.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
it was 3.2, I checked yesterday. Whatever changed X committed to the kernel between 2.8 and 3.2, lies the culprit.

its not user error, as I've done all the stuff normally recommended to noobs lol, and my meter says I may know a little about what I'm taking about ;-)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Confirmed, camera does not work for me in 3.3 or 3.2, but it's fine in 2.8. I'll stick with 2.8 for now until we can figure out the cause.

Tom
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8trix:
That is weird because I have been on 2.8 3.2 and 3.3 on 07/02 nightly and 07/04 nightly and have had no issues with my camera messing up actually the whole system is runnning great it may be specific to certain roms
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lnfound:
Upgraded from way back to 3.3. Broke the camera, no big deal for me. Was on track for 4hr screen on time but after 50% battery started to drain much faster and I'm back to about 3.5hr. Does everyone have similar results in battery draining faster as you get lower?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locoman_:
I'm running v3.3 on the 07/05 cm9 nightly and everything is working great. I had a minor issue where the camera app said something about "can't find" so I backed out of it and tried again with no problems.

FWIW, here's my process. I know it's 'unnecessary', 'redundant', whatever, but I never run into the issues that other folks run into so I'm sticking with it.

boot to recovery

wipe both caches 3x

flash nightly

wipe both caches 3x

reboot and allow to timeout

boot to recovery

wipe both caches 3x

flash InstigatorX's kernel

wipe both caches 3x

reboot and allow to timeout

Thank you InstigatorX!

.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] :
Camera not working for me either on a fresh install of Chimera RC2
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] teeg07:
On armyvets aokp build 40 and running kernel 3.3 and my camera works fine.

wiped both cache's after flashing... but thats about it. was on 2.2? before this one.

so far so good on my end. running badass Governor now.

*i've been running this install a few days before i flashed the new kernel this am.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RabidSmurf:
My Camera was broken but it's now working again.

I have been clearing caches and flashing gapps and various things and noticed that it suddenly works now and no amount of using it seems to break it (on the 3.2 kernel).

My only thought is that possible the use of AromaKoK mod may have inadvertently fixed it since I believe it copies/re-copies some core files (Don't quote me on that).

Edit: Nevermind, broken again...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] hechoen:
Just flashed Chimaira RC2 then flashed kernel v3.3. Camera is working fine. Looking forward to seeing where this kernel goes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] InstigatorX:
I think I've got it narrowed down to the new toolchain (4.6.3). Not sure why it works for some and not for others. I've v3.4 out for some testing and will post once I hear back.

One thing that could be having an effect on some is that I've been tweaking the voltage along the way. If you've undervolted in System Tuner (or the like) this could have an impact. Make sure to set voltages back to default before you reboot to CWM and install. Otherwise it could UV you too much and cause weirdness.

EDIT: Posted 3.4 since I might not be able to tomorrow.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kuraijay:
my camera is working again thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] UZ7:
If this is the same as the test build, pretty good so far :)

CM9 07.05.12
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lnfound:
AOKP B39, camera is back to working in 3.4 after breaking in 3.3. I wiped caches after flashing this time rather than only wiping before, those who reported that in 3.3 seemed to have no issues.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locoman_:
3.4 gave me a bootloop. I'm running today's nightly 7/6.

I'm going to see what happens with others before i try again.

btw, i always use the defaults never use other apps to uc or anything.

Edit: Wanted to mention that I wiped both caches after installing 3.4 fwiw.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seemles:
got boot loops here on 3.4 went back to 3.3

also I'm running my own build of CM9 compiled yesterday, I did a clean install and my camera didn't work from the start even before I installed 3.4.

If i restore a backup from a few days ago which was a nightly and stock kernel camera is fine. weird??

I think the new tool-chain is borking the camera. or something is still being left behind after wipes and formats.

I'm going to try and odin to stock then to CM9 and see if that flushes it out.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] USHERROB:
^^my camera was getting borked when using aroma667 on latest cm9 nightly and 3.3.... camera only messed up when i installed animations.... i reflashed cm9 nightly and all was well, then installed all boot, inverted apps and such and all was well, just no cool psynshift animations or anything
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Boot loops here as well with 3.4 on CM9 7/06 nightly. 2.8 works.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8trix:
This is my battery life running /07/05 nightly and 3.3 kernel no camera issues looking to flash 3.4 but im affraid to get bootloops

EDIT: Flashed 3.4 fixed permissions before and after flashing and everyting is working no bootloops however I am on nightly 07/04 so once a few more nightlies come out I will try to flash a new nightly and see what work and what doesn't.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] seemles:
OK so I odined back to ucle2 the went straight to a cm9 build I compiled yesterday and no camera. I don't believe this kernal is the problem I think its cm9. Just a guess though. I'm going to flash a nightly and see if that's any different.

OK so just flashed the most resent nightly on top of my own compile from yesterday all I did was wipe cache and dalvik cache, camera works! So confused! Happy but confused lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] emmellst:
Hooray! Thanks for the work! running he latest cm nightly with 3.4 kernel the camera works again. Loving it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locoman_:
Hi. I just wanted to be clear about this. You're on nightly 7/6 and kernel 3.4 is working for you?

Could you please list your installation process? I'd like to see your process kept you away from bootloops...

Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jose makalolot:
+1 bootlops also on 3.4... now I,m back to 2.3.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
I'm on 7/6 nightly, 3.4 kernel, no issues at all, no bootloop.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BaconStep:
Boot loops on aokp b40
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] InstigatorX:
For those of you with bootloops on v3.4, can you test these two different builds and report back? Let me know what version/build (e.g. AOKP or CM9 and the build date) you're running on.

http://d-h.st/pG9

http://d-h.st/PHj
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8trix:
I wiped cache and dalvik 3x and fix permissions and install then repeat 3x clean cache and dalvik and fix permissions then boot let sit for a minute or two and reboot to twrp and fix permissions again also if you want togo the extra mile clean app data on apps to make sure you dont have any little issues I am on latest nightly and 3.4 and no issues found this is though the way I alwasy install things to just make sure im not gonna have a problem

---------- Post added at 01:20 PM ---------- Previous post was at 01:15 PM ----------

Hey man btw thanks for going up to 1.836 on the kernel didnt notice till I ran a benchmark that its one step higher thanks so far no issues found but will test all day with fresh battery to see how the battery life is compared to 3.3
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] merlen:
Running cm9 nightly version 7/6 with original 3.4 boot loops. Second version booted after a couple soft resets and camera works again. Did not try version 3.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jose makalolot:
InstigatorX-CM9-Kernel-3.4-1728.zip has no bootloops on 7/6 cm9. Thanks.

Sent from my Calculator with Android.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] itwin504:
Both works now, but using InstigatorX-CM9-Kernel-3.4-1728.zip. Thanks a bunch. Loving the badass governor. On CM9 07/05.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] raider03:
Alright! Camera working again for me with v3.4.... thanks instigator...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locoman_:
I gave "http://d-h.st/PHj" a shot and no bootloops (CM9 7/6). Seems to be running fine, thank you. I'll test it more thoroughly later.

Edit: Phone started freezing and acting a bit laggy. I can't say for sure it had anything to do with the the kernel but I dropped back to 3.3 and it seems to be ok now.

.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ericos123:
InstigatorX-CM9-Kernel-3.4-1728.zip

ran on CM9 7/6 - worked perfectly no issues
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] norcalsfinest:
Same here on 7/5 Nightly, no previous or current UV. Reverted to 3.3
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scottx .:
Damnit man! Stupid phone was in my pocket most of the morning.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] InstigatorX:
I noticed the mobile signal changed right about the time the battery dropped more precipitously. Any idea why? Also, check bbs next time to see what kind of wakelocks were present. I've seen the same thing happen with some Google services when signal/connection is bad.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
+1
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ckck543:
Thanks X everything works great in the 1728 test build :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] foreverzero89:
cameras back with 3.4 on cm9 alpha 5 i wonder when we're gonna get a beta or the next alpha for cm?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
There is a placeholder for RC1 on the CM sites.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] dakpluto:
Was going fine all day and then started to get really bad reboots. Flashed the first test of 3.4 and that seems to be working now.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] IEatKittys!:
3.4 doesn't seem to work for me. Neither does the other two test builds he posted after.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tacotino:
Everything workin great on 3.4 no problems

Cm9

instigator kernel!!! OC/UV

custom ballz
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] raider03:
Instigator on v3.4 you locked underclocking? I see you overclocked to 1.8 but I don't really need that much power so I tried to switch to 1.51 but it doesn't stick...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] norcalsfinest:
Couldn't get any 3,4 to work by itself. Ended up flashing -1728 over the other one to get it to boot
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8trix:
im on 3.4 and my undercloxking sticks wih setcpu profiles for screen off and in call profiles at 486Mhz
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NIKEstickER:
Ive been on v3.4 for about 10 hours and i can already see a difference in battery and loading times. and CAMERA WORKS!! very solid kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ckck543:
Okay so something weird just happened to me . I flashed the kernel 3.4 1728 test version and everything was running great. I put my phone in my locker and went for a run at the gym and when I got back it was warm and wouldn't turn on. I had to hold he power button to force a reboot but after it booted up it is working well. Any input or suggestion would be great :) thanks (I can't recreate it sorry)

Edit: paranoid android R2 is what I'm running (based of the nightly today 7/06)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Locoman_:
I'd suggest flashing an earlier version that didn't give you any problems. It's the nature of the 'experimental'. Maybe also edit your post and give some more details to help InstX... the rom and version you're on...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] boobah204:
8Just had random reboot into boot loop on 1728. Was listening to music and it suddenly went into a beep that sounded like the emergency broadcast alert system. I thought it was part of the track because I'd never listened to it before then the beep stopped, my phone vibed, I pulled it out off my belt and it was bootlooping. Badass governor default settings. Phone was not warm to the touch. Flashed 3.3 and everything immediately back to normal. Nothing was running in the background but I got a tapatalk pm notification as soon as I got it back on, that may have been the trigger. (Although prior to that I had gotten several while listening to music)

Edit: oh yeah forgot the part about being on nightly 7-6

Edit again: flashed about a half hour after posted, so about 9 hours was running smoothly, downloaded said music from amazon mp3, stole some other music with ttorrent, used phone heavily till 50% battery, then tethered a blackberry to listen to Pandora while this phone was plugged in. Also constantly texting and talking on the phone. Was 100+ degrees farhenheit outside and I tried to keep the phone in the shade but had a hard time keeping it cool. No problems at all during this abuse. Not until after sunset, with the phone cooled off and what I would imagine to be a comparatively comfortable state for a phone to be in (for about 2 hours i guess) did the problem occur.

So I think maybe it's random.

Sent from my part of the problem
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jose makalolot:
Anyone able to get deep sleep with working 3.4? My phone won't. Twas working up to 3.3.

Sent from my Calculator with Android.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8trix:
Try flashing again or maybe the other links instigator put up a few posts back I am on 3.4 and my phone goes into deep sleep if left alone for a while no issues here
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] endlessevo:
Having the same issue, I've tried all 3 of the 3.4's.

I've cleared cache wiped data everything I could think of and I get boot loops on the 2 experimental ones 30% of the time the rest of the time it flashes Samsung and turns off.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jose makalolot:
Already tried the 2... since the 1st gave me bootloops. But, no deep sleep for me.

Sent from my Calculator with Android.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
on chimera rc2 with the 3.4-1728 kernel test build and fully functional here. Deep sleep as well as camera are functional, running smartassv2 and undervolting by around 62.5-75 mV. Also using single CPU sleep mod, with no issues

As for the boot loops, running like a broken record, make sure u have formatted both dalvik and regular cache before and after kernel flash for overkill protection. I used the dark side wipe cache only mod on 5.0.26 with no issues
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] UZ7:
Lol CM9 07.06.12 w/ 3.4 driving w/ GPS and Data. Badass 192/1.8 kinda ate up a lot :p but not too bad.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Sully6789:
I use Eugene373's CPU sleep app from the T989 forums and deep sleep isn't a problem for me on 3.4-1728. Can't comment on whether the phone deep sleeps without it on the new kernels from X, but you could try the app out and see if it helps.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
that script wuz actually giving me issues with battery life in deep sleep, at 3-4% per hour. Without it, I'm at 1% with the same kernel. In recommend removing it, as this kernel has integrated mpdecision
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] quikt:
1728 worked for nightly 7/1 where the previous kernels boot looped or no cam. 1728 also working on 7/7 nightly. Wipe cache dalvik x 1.Thanks!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] foreverzero89:
3.4 started rebooting my phone, had horrible life and wouldn't deep sleep. had to go back to 2.3
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] InstigatorX:
Try the two builds a few posts back and report back please. 3.4 is oc to 1.832ghz and doesn't some people's phones.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] unibombz:
3.4 boot loops my phone, using 3.3

however not quite sure why you can not set the max CPU freq, it always stays at 17**
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
same here tried it in set cpu and system tuner but i couldnt under clock. this was with 7/7 cm9 nightly and i tried it with both of the 3.4 versions you posted a while ago
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] surge27:
Just downloaded 3.4

-Camera works

-Able to set and keep at 1.8

Will report back later on battery life and if there are any issues
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
can you underclock it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] surge27:
After trying several times....nope.

One difference I noticed is phone doesn't get hot compared to using Cymbaline
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
read and weep :-D

I would've got over 3 hours but I started at 96%, didn't fully charge lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] chinthekng:
Your phone must be on steroids or something :eek:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rwelsh09:
I flashed the second link and there was no boot loop, camera is working too. :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roderick08:
Which link u used my camera not working
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rwelsh09:
http://d-h.st/PHj
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] unibombz:
3.4 is boot looping for me (i727R) , and 3.3 the camera is not working.... I am back on chopsticks stock ROM kernel (seems to give me better battery life being that it is only clocked to 1512mhz)

As well can we under clock (on instX kernel) the CPU, stays at 1782 and i wouldn't mind keeping it down to 15**

Thoughts ?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Killer Okain:
This one worked for me with CM9 6/06. Camera works, but its buggy, which I'm pretty sure is a ROM issue. It'll force close when changing settings with the camcorder, camcorder effects don't work. Again, these are ROM issues.

A few things I've noticed with respect to CPU settings; It seems only badass will overclock, the others revert to 1512 regardless according to cpuspy. smartassv2 is smoother than badass.

Testing for battery life but at first glance it appears to deep sleep just fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] unibombz:
Yah I tried both reposts of the kernel above... one boot loops, and the other boots, gets to the lock screen, is unresponsive then reboots... so I am not too sure.

using : [ROM][CyanogenMod 9][TeamChopsticks][Alpha 5 - 6/14]
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] InstigatorX:
I believe the camera issue is a ROM problem. Happens to me on stock.

As for the 1512 revert for non-badass governor I haven't seen that. Does it only happen on the test builds or any of them? Do you have any scripts that are setting it to 1512? or is your init.qcom.post_boot.sh customized? Not saying it isn't true, just hope there isn't yet another bug to squash.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Killer Okain:
Well the test build of 3.4 is the only one I've been able to get the camera to work on, so I can't say if the result is the same on the others, reverted back once the camera wasn't working. I'm going to flash the regular 3.4 now and test the governors. No scripts and no customizations. I tested the speed with a couple games I thought would max it out (as well as web browsing etc) and checked the results in cpuspy.Thus far only badass will go above 1512, even performance was stuck there.

Edit: After flashing the regular 3.4 I found the other governors would go above 1512, so I guess it was the test version. Oh and this time my camera works with 3.4, so go figure. Setting 1836 and performance results in a very smooth/fast experience, but probably isn't too good for hardware longevity or battery life.

2nd Edit: OK new problem. With 3.4 I can't get any governor to max out BELOW 1836. Whenever I lower the max setting and exit CPU settings and return, it has reverted back to 1836. CPUspy comfirms its still maxing out at 1836 with every governor. I can change the min, but the max stays at 1836. What did I do to this thing?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] thatlonedude:
Use setcpu to make a profile and set the max at whatever you want
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roderick08:
The link worked super fine me camera worked and still Oc to 1836
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] surge27:
Doesn't work. Kernel not compatible
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] thatlonedude:
That's really weird, it's working just fine on mine at 810, what governor are you using?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] RK:
Hey

I found this issue with the headset button for all the kernels based on Hercules source. I have reported it before on the cm9 thread but today I narrowed it down to the kernels built with T989 source. Full description is in the following post

http://xdaforums.com/showthread.php?p=28455712

Hope you can solve it for AOSP roms and mohan can solve it for STOCK base roms.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] surge27:
So....it works but didn't know until checking Time in State for actual usage.

Set it at 1080 MHz Max and 384 MHz min.

Used smartass governor.

Only question I have is what's normal temp for the phone????
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] InstigatorX:
It's not you. There's something called DVFS in the build that prevents underclocking. I can make multiple builds with different max speeds. I'm trying to figure out how I make it work with DVFS, though.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] icenight89:
OK, at this point I'm not even bragging, more in disbelief? This is off a full charge with no wifi use whatsoever.

its probably becuz my phone lets me under volt like crazy, -87.5mV on top of whatever instigatorx did in the 3.4 1728-hc build. I also have max at 1188 and CPU governor is set to smartassv2

rom is chimera rc2 and in-built rom control was used to set those, no other CPU apps whatsoever, except a custom vdd_tables init.d script
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Dismal Shadow:
The one in OP gave me a bootloop, the second link works. Haven't tried the first one.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BaconStep:
Not sure if this has been posted but this kernel works fine on MIUI
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sumkee:
Not sure if I'm the only one, but the changes in Max frequency dont' stick, but the ones in Min frequency do. I'm currently on latest CM9 nightly (0709) and 3.4 - 1728 build and governor is smartassV2.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sk8trix:
Just noticed that that even with setcpu profiles of 1512Ghz it still goes up to 1.8 Ghz either way battery life is still good so its not a big deal.Is there going to be an update that will fix it so that the max frequency sticks though?

Also might it be a rom issues??? just wondering anyways still a kick ass kernel.