yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] baddgoat:
Download fails on devhost, and mirror doesn't contain 1.3 version

Edit: devhost finally worked. Took a few times. Thanks for this. About to try on latest PAC nightly
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] baddgoat:
Can't get it to boot on latest 10-14 PAC. Sucks, cuz man this kernel is beast
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] x2o:
I couldn't get it to boot on the latest PAC nightly either (10-16).

Might this be cause we're on 4.3.1 now?

Hope we can get back to using this kernel soon :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
It's running fine on first boot on Dirty Unicorns latest build which is also 4.3.1. The issue is rebooting. Whenever I reboot it bootloops. Wiping cache and dalvik fixes it so I'm thinking it might be an app. I just put a new OS on my comp so I haven't installed ADB yet. I can reproduce it whenever I want so I'll try to get a log from boot this weekend. Other than that this kernel is rock solid. Wheatley and BFQ with some UVing seems to get the job done on my phone. Snappy and above average battery life.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Cl3Kener:
Hey guys!

Well, I'm seeing some weird theories as to why the kernel is not booting on PACman. The truth is PACman has several init.d scripts (about 12) some of which appear to be necessary for it to boot. I've rebuilt the kernel with some new tweaks to try out some LZ4 compression and a few things and I've also changed the install method to see if it will work now on PAC as well. It's sad because my other install method works on every other ROM but PACman so it is a compromise (hopefully this install method won't mess up other ROMs)

[MENTION=5451511]theesotericone[/MENTION] it sounds like you need to try a different recovery. You issue sounds exactly like the corruption bug that delayed 4.3 from coming to the SR in the first place. TWRP 2.6.1.0 is what I use but anything from about 2.6.1.0 and beyond now works with SELinux so that you hopefully won't have data corruption bootloops on reboot. I don't know about CWRM because I don't use that maybe someone else can fill you in on that below (hint hint)

Anyhow, here is my new Experimental kernel for you to try. http://d-h.st/QKv Let me know if it boots on PAC or not.

Cheers!

Cl3Kener

PS if it doesn't boot see here for how to replace boot.img and modules in PACrom before flashing... http://xdaforums.com/showpost.php?p=46532433&postcount=1916
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] berniesteven:
Latest build is the best so far on carbon.

SGH-I727 Peace
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Is this one reason why the kernel takes longer to display the bootlogo and load the os?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
LOL. I wish it where as simple as the recovery. I've used TWRP 2.7 as well as CWM 6.0.4.3. It reboots just fine from either recovery with just the ROM and Gapps installed. As soon as I install my apps the problem starts. So a little Occums Razor leads me to believe it's an app. Hence the need to get off my lazy arse and log it. I'm upgrading Ubunutu to 13.10 now but as soon as that's done I'll get adb on there. If you want a copy of the log when I get it let me know.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] x2o:
Seems no matter what I try I cannot get this to boot with PAC.

Tried a dirty flash and then a clean flash the standard way, the init.d scripts never finish and it never gets to building the dalvik.

So I tried placing the boot.img and .ko modules into the rom zip itself as you mentioned, could not get it to work either. Same thing, hangs at the boot screen looping endlessly. I'm assuming it is erroring out on a script which ends the init.d, so it never gets to building the dalvik and the actual boot.

I tried baking the files in both ways, once after extracting the rom and then rezipping it, and the second time I just swapped it updated/replaced the files in the zip without extracting.

Not sure what it could be at this point
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Been running LZ4 with CM10.2 Nightly for 5+ hours now and very tickled with it so far. No crashes. No RRs. No lockups or slowdowns. No graphics glitches. (All at different times doing different things of course.) No black lock screen from wakeup. Just totally impressive!

Been testing since the first version and this one has proven to be the most rock solid so far. OC/UV has been holding really well and want to try running through the governors again if it keeps up like this (I am a fan of the Wheatley gov but it has been unstable for me with prior versions. It has been getting stuck in a max freq lock and the phone crashes from it forcing me to reflash and wipe cache/davlik to reset, so crossing fingers it will prevail this time).

Awesome work sir and much thanks! :thumbup::thumbup:

Sent from my SAMSUNG-SGH-I727
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
SO, ADB up and running and you guessed it. Won't capture anything because it never gets to the OS at all. Android can be so frustrating at times. lol Looks like I'll have to figure out what app it is the hard way. Lucky for me I only have about 40 of them that I use.:eek:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ronnyhawks:
For you and any others having booting issues- I flashed this kernel and it did absolutely nothing for about 3 whole minutes. Then it displayed the Samsung logo. Then about a minute later it finally showed the boot screen. Then after the boot screen finished, it optimized all my apps, then when it got to "starting apps" it hung for a minute then rebooted itself. Then it went through the boot animation again and booted right up. I think it just takes a little patience and time. User error does happen as I thought it didn't work 2 times before. This time I gave it a little more time and it worked. Hope this helps some people
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ronnyhawks:
It takes about 3-5 minutes of the phone doing nothing before it actually gets to the boot animation. If you aren't letting it sit long enough it wont get to the OS. Read my previous post. I think people having issues booting is just user error. You need to let the device sit for about 5 minutes and let it go through the boot animation and optimize apps then it will restart and go through the boot animation again then will boot up perfectly fine. i thought it wouldn't work also but the last time I just let it sit and do its thing and I sat and watched and timed everything. It does work. Again I hope this helps some people

Edit- tried flashing today's CM10.2 nightly and it is not compatible with this kernel. It did boot but bootanimation only showed light blue and yellow flashy screen and when it did boot everything was yellow. Flashed back to the 10/18 nightly and all is well again.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Have you tried the LZ4 version of the kernel yet? I'm running my own CM10.2 build from this morning with this kernel and it is working great. Granted, there was a change to the qcom/display-caf driver code that was added today that I tested over the weekend that gave me the same issues and some artifacting, so I reverted the driver to a previous version and that fixed my problem. I imagine that any kernel before today is no longer going to work until it is updated to work with the new driver. Can anyone else confirm this information?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ronnyhawks:
I will test and report back soon. Anybody have issues to where only a factory reset will get the OS to boot?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
The issue your describing in the first post is not normal. Something is causing this lockup. At first boot it always takes a little while for the phone to get itself set up then load into the OS. Subsequent boots should go smoothly without any issue. It's not booting for me after the first boot. I can let it sit for ten hours and nothing changes. It never loads far enough into the OS to allow ADB to register the phone or I'd already have a log of it. I still believe my issues are caused by an app that was built on SDK 17 not 18. I'll take some time tonight to do a fresh install and add back my apps one by one rebooting in between.

As far as your second post goes I've always been able to clear up the non boot by just wiping cache and dalvik a few times. Sometimes it will boot up sometimes I have to go back into recovery and wipe them again. I've never had to factory reset to get the phone to boot. But if your factory resetting your erasing the app(in data) that is causing the issue. So it would make sense that it would boot just fine if my hunch is true.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
I get this when I flash between ROMs, but not between updates. As [MENTION=5451511]theesotericone[/MENTION] mentioned, wiping cache/davlik fixes it. Not sure if it is a 4.3.1/kernel issue or a recovery problem for our phone. I have been running TWRP lately, but I can check the other recoveries later to see if the problem persist across all of them.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
I've tried all the 4.3 recoveries except TWRP 2.6.3. They all seem to work fine. The issue I'm facing in not being able to reboot. Never even gets to the boot ani. I'm reinstalling Dirty Unicorns right now. I'm going to leave Moretz on there then reinstall all my apps. It's locked up with Moretz before but it never hurts to double check. If it locks up on both kernels when rebooting it is most likely an app. So the process of elimination will begin. lol If any one has any better ideas please post up.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ronnyhawks:
It is not an app causing my issue unless its a system app that comes preinstalled. I tried on a fresh install also so I know that its not an app. Wasn't even signed I to my gmail yet. I'm still wiery on testing the test kernel being as I've had to factory reset my phone over 5 times in the last couple days. not even a restore of my backup would boot.....

---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------

I've tried wiping cache and dalvik it don't work. All that works is a factory reset. Believe me I've done this almost 10 times in the past 2 days and that's the only thing that gets it to boot. I'm not too worried being as my main device is a T-Mobile HTC One and the Skyrocket is just my spare for when the One is on the charger lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
Well it's not an app. lol Just rebooted DU with Moretz after installing my apps. It rebooted fine about ten times in a row. Flashed Uber and boot looped at the boot ani. I'm still able to wipe cache and dalvik to get it to boot. It still loops at the reboot though. So yeah it's something in the kernel. Conflict of scripts maybe? It's such a great kernel I'd really like to see this figured out.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Cl3Kener:
3.0.101

Hey everyone,

Well 3.0.101 came out which is the last 3.0.y kernel update in the cycle. I decided to rebuild again in hopes to fix some issues. I'll be honest, I don't understand why there are so many issues over here with these kernels. The same kernel and tweaks works great on the Hercules and Quincyatt so I've removed everything but the actual kernel (so everything but boot.img and modules) and I've made two new kernels. If you don't follow the CM BBQ here is the deal. New GPU updates were pushed yesterday which means that the current release kernel on the OP will not work in future CM nightlies starting today OCT 22 and onward. So I made a kernel compatible with the new GPU configuration and one with previous configurations. I have also made both of these with Linaro 4.7.4 to see if this make the incredible improvement already seen on the Hercules and Quincyatt. Let me know how these two kernels go. If everything works out I'll make another release. :)

Here are the links

UBER - PRE OCT 22

UBER - OCT 22 and Beyond!

Cheers!

Cl3Kener
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bzzybfrm313:
Never had a problem with any of your kernel's from here or the Hercules forum:good: Thanks again keep doin what your doin
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Thunder22:
These kernels are great. No issues at all so far. Thanks for being awesome.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Lokas0:
Confused

Im confused wich kernel i should use for PAC 21/10? Since its from yesterday and i dont know if it has to be the before or after 22 october? :confused:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Not sure if its like CM10.2 but I downloaded the one for future builds and it worked for the 10/21. Backup your boot if using TWRP and try the latest one first and just restore your backup if it doesn't work. BTW CI3Kener awesome work on the kernel so far running awesome on CM10.2.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] theesotericone:
First thanks for keeping up with these. Second I'm running DU so I can't speak for other ROMs that seem to be working great. I just got done trying a few things. First I removed all the build prop edits from the latest kernel and repacked it. Flashed fine but still hangs on the boot ani. Then I checked modules vs DU and found that DU didn't contain frandom.ko. So I removed that then reflashed. Same thing. Then I tried removing all the scripts from the kernel. Go a status seven on that one because of a conflict with the updater-script. I've run out of time to play for tonight but I'll try a few other things(like editing the updater) when I get some time. It is strange how only a few are reporting this and others have zero issues booting and rebooting. To give you an idea of how much I like this kernel I ran it for over a week even with the reboot issues. My fix was simple. Don't reboot.:laugh:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Not to speak ill of your other kernels, but so far this one is the best I've noticed on CM10.2!:D It is extremely smooth and great battery life. One thing I was wondering. On the stock CM kernel, when you charge your phone when it is off, you get text in the middle saying what battery percentage it is at, do you think it would be any trouble adding that in? Thanks and keep up the great work!

Edit: Just in case you didn't see my pm, the 10/23 nightly for CM 10.2 has caused me to have the android.phone has stopped working message as soon as I flash the kernel and boot the system. I made sure to follow directions and have done the same wiping the cache after flashing and once it optimizes the apps is when the error pops up. I have tried downloading the nightly again and it only pops up the error when the kernel is flashed. My comment above was on the 10/21 which was the first to include the new GPU changes and I made sure to check the MD5 and everything checks out. If you need any help, I'll be more than happy to assist.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] holeindalip:
I'm getting the same error also using the 10-22+ kernel on the 10-23 nightly
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] eagle0042:
Same here, using 10/24 nightly. Clean flash + gapps works. But then com.android.phone FC's once the kernel is flashed. I tried both flashing the kernel the same time as the ROM. And then I tried letting the ROM boot once, then flashing the kernel. Neither worked. Using TWRP 2.6.3.0.

Edit: I've attached what I could grab from a logcat, if that's any help.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mesiu84:
Worked great until last CM update :( now screen isn't working properly. I've returned to normal kernel and all is fine now, except BLN which isn't running anymore :(
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
And for confirmation, I have the same error as well on 10/24.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Snoop05:
ya, not working for me too, yesterday i flashed it 5 times, on clean CM 10/24, so i'm sure

while booting, cyan screen with magenta stripes, on system cyan is strange orange and getting com.android.phone error.

:good: hope you will find what's causing it
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Cl3Kener:
Hey Everyone!

From the comments, it appears that the ramdisk did not append correctly. Here is a quick update to see if I got the ramdisk on the zImage correctly this time. Since the Pre Oct 22 kernel works I won't mess with it. This is just a quick remake of the post OCT 22 kernel to try with the very latest CM nightlies. Let me know if this works so I can make two release and another BLN kernel with the new gpu updates since I see a few of your would like an update BLN kernel to work with Post OCT 22 builds! :D

Here is the link: http://d-h.st/dEf

Let me know how it goes!

Cheers!

Cl3Kener
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
Not sure about other people but I am still getting the same error message. I did dirty flash only this time then flash the kernel but after it didn't work, I just installed the latest cm nightly, no error message. Like you were saying a few posts ago, its weird how the Hercules is having no issue.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
Me too, again on CM10.2 10/25 nightly.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] bzzybfrm313:
This one seems to be working great for me on florendroids latest slimhalo which was just updated today

Thanks again for this amazing kernel
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
It must be something that was merged after the 10/21 nightly for the skyrocket that is causing the error because the kernel with working perfectly with awesome battery life and then the 10/23 nightly on, that phone error. If you have your 3.0.101 kernel that is for Hercules ported over yet, I can see if that fixes it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
I can say in this case it's that weird 'Middleware' commit by Koush. Here It clearly isn't implemented properly and I revert it in my roms. This is a ROM issue, for now.

As for that, you have to wait till it is fixed or somehow find a rom that has either had some good original code to resolve this obscure feature or one that has reverted it altogether.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] eagle0042:
Thanks for pointing that out. I actually noticed that commit today, and saw that it referenced files in my logcat, so I wondered if there was some connection there. But I do find it strange that: (1) it doesn't seem to have any effect on Herc (based on what he said) (2) Looking at that commit date/time, wouldn't cm 10.2 10/23 nightly work fine with this kernel? (3) Why doesn't stock cm10.2 have the same issue?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Cl3Kener:
Hey guys,

It is has been a little while. I think I might have finally fixed the NEW GPU error. See if this fixes it! http://d-h.st/VOc

Cheers!

Cl3Kener

PS I appreciate your patience.

EDIT: Forgot to mention that I added FIFO to the IO Scheduler list! Try that out and see what you think!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
It boots. Will play with it and report back any funny business. :good:

Edit: My phone says to tell you thank you and it loves you. lol. Awesome work dude!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] holeindalip:
It boots and runs fine on 11-6 nightly
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
I don't know what the problem is on my phone, but it just constantly reboots with this kernel. After install it got to 'updating 8 of 137 app', and rebooted, the next time it got to 'starting apps' then rebooted, after that, it got to the lock screen and rebooted. Twice after that it would boot, and the screen would shut off after the timeout, like it normally would, but when I pressed power and slid to unlock, it would hang and then rebooted. I reinstalled the ROM (CM 10.2 11/7 nightly, my own build) and it has been fine without it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
Which recovery are you flashing with? I ask because this kernel seems to have issues with TWRP 2.6.3.0. I personally just drop back a version to flash the kernel and then flash back to the current recovery for everything else. Haven't tested in CWM in a while but haven't heard of any problems from that recovery in relation to this kernel.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nawlage:
Can't get it to work on the latest DU 2013-11-06. The newest version of the kernel is the only version that will let the phone boot but its all jacked up with the yellow/purple/doubled/huge lettering. Other uber versions show the Samsung splash then the DU animation then the animation freezes and the phone reboots and shows Samsung again then it sits at the black screen until i pull the battery. I was somehow able to get the previous version of DU running with a pre 10-22 kernel but it took several reboots and cache clears and permission fixes.

For reference:

ROM: Dirty Unicorns 2013-11-06

Tried recoveries: twrp 2.6.1.0, twrp 2.6.3.0, twrp 2.7, cwm 6037

uber versions: linaro 10-22-2013, linaro 10-25-2013, 11-06-2013

with cwm 6037 all three of those kernel versions result in the phone booting completely but then having the wack display issues.

Shot in the dark: would updating the gpu drivers make a difference?

http://xdaforums.com/showthread.php?t=2417738
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gr8tech:
I can confirm a RR issue with the CM10.2 11/7 nightly as well. For me it seems to happen every couple of hours and I probably wouldn't have noticed it if my phone hadn't vibrated on the table for me to look and see the boot screen this morning. When I check my processor stats, it didn't appear to have been deep sleeping too well, but not to say the problem is with deep sleep because it was doing it. 11/5 worked flawlessly, 11/6 had a slight RR hiccup a couple times upon first install but with a couple adjustments to the settings and it was happy again, but 11/7 is definitely making it throw a tantrum every few hours. When I get a chance away from rom development over the next day or so, I will reinstall again and try to capture some logcats for you to troubleshoot with. I also am wondering (but doubt) if the issue may have anything to do with the build updates in the 11/7 build:

3929a21 kernel: add support for bzImages

3d7cb50 kernel: do not assume arch is arm
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nawlage:
Bamp.

Would really like to utilize this kernel in DU.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Tsk_Tsk_Tsk:
For those of you who have installed this kernel and have it working, what ROMs are you using?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nawlage:
This
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Smittiegee19:
???

Sent from my skyrocket running something better than yours! BOOM!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onealvideo:
He is asking the same question.

Most people say bump...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nawlage:
Or +1
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Boot_Derran:
LiquidSmooth from10/25
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nawlage:
i just found success with du_2013-11-06 and 3.0.100-UBER-LZ4 from Fri Oct 18 10:12:33.

i thought i tried every version posted in this thread. maybe not. either that or it decided it wanted to work this time around.

*

NOTE

after flashing the kernel and restarting the phone boot looped once. on the second loop it came out of it and started up.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nawlage:
So I made a backup of my du and uber combo and flashed a different rom to try. Upon resorting my du/uber combo it would do the boot loop but after the second or third it would flash the Samsung logo then hang at the black screen. I ended up having to do a clean install of du then restore everything but boot from my backup then flash uber again. Then it worked after two boot looops.