yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] thomas.raines:
I need a logcat. It might be the ROM because torch works fine in my PA, and I haven't had any weird FC's

Been playing solitaire for about 9 hours off and on with no issues and at 75%... with wifi and radio on but no connections... changed my scan settings to every 3 seconds and my accounts to sync every 5 minutes too just to see what I can get out of it...lol
[Samsung Galaxy S Blaze 4G] thomas.raines:
adb logcat -v time

Also helps to tell me the time in which you experienced your error...
[Samsung Galaxy S Blaze 4G] thomas.raines:
I'm getting about a 1.5 second camera lag but no failure to connect. But what I am seeing in your logcat appears to be ROM related issues. I'm going to keep studying things and see... Because I think it is a library issue... Thanks for the logcat...

The more I play with it the worse the lag gets... I have a good Idea what it is now... Thanks!
[Samsung Galaxy S Blaze 4G] skullreapper66:
I'm having a couple of problems with customizing init.d script for battery life. I've followed the instructions to the best of my noon abilities. Adding a # to lines 11- 19 and removing it from the other lines presents difficulties. Maybe I just can't read, but I'm finding it difficult to discern exactly where to add and remove them.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Probably because I forgot to update the op when I edited the scripts... My bad...

They are updated now... my apologies. A word of advice to everyone, pay more attention to the code and less attention to the line numbers...
[Samsung Galaxy S Blaze 4G] thomas.raines:
v3 is now up. It looks like I got the camera issues fixed. There is still some slight lag, but it is acceptable... (loads in about 1.5 to 2 seconds)
[Samsung Galaxy S Blaze 4G] gwimmel:
Awesome, thanks man! flashing now, I'll check back in with my results tomorrow. :good:

Edit: I can confirm the camera works a lot better, also torch somehow also got fixed for me, it works better than ever before now! (still using 11/16 nightly CM10 here)
[Samsung Galaxy S Blaze 4G] gwimmel:
Alright, I've been using this for 3 days now and everything has been working really well until today, i finally got around to driving and tried out the GPS with google nav, all 3 times i tried it, my phone decided to reboot after about 10 mins of driving. I don't know how to make logcats (yet, i'll get off my ass and figure it out soon), but it seems to pretty consistently crash when i use google nav. Hopefully knowing this can help get us one step closer to finding out what keeps causing SoD. (still using LZv3 with CM10 nightly 11/16)

unfortunately, for the next few weeks I'm gonna have to revert back to CM9 because i need GPS to work (my sense of direction really sucks), so i can't do much more testing on this v3 kernel.

Thank you again for all your hard work on this, I'm really looking forward to having myself some stable jellybean. :3
[Samsung Galaxy S Blaze 4G] johnb380:
I have a logcat of a random reboot I just had... I'm running Aokp not cm10 tho

http://db.tt/SRYBWXO8

Around 847 it happens give or take a few secs
[Samsung Galaxy S Blaze 4G] johnb380:
Here's a logcat for you random reboot happened around 241.30

http://db.tt/V29rzNeF
[Samsung Galaxy S Blaze 4G] thomas.raines:
Updated source code for the vendor files. Check the commits in my github
[Samsung Galaxy S Blaze 4G] thomas.raines:
Thanks for the logs. I need to know:

Did you "prune" these logcats? It doesn't look like it but there are key things that I look for on a reboot issue that aren't there.

How did you flash this kernel? Did you flash your ROM, flash gapps, flash kernel, or did you just push the boot.img to you ROM.zip and flash?

Lastly, I see a huge error with libc.so. Which is probably a ROM error not kernel.
[Samsung Galaxy S Blaze 4G] johnb380:
No didn't prune them I use catlog to save them and I flashed rom Gapps kernel in that order Cuz this kernel reboots the system so I always flash last... But Idk if it is rom or kernel but just thought I'd let u check it out
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yeah, something is definitely wrong between the ROM and kernel. I need you to navigate to /system/etc/init.d and give me a list of the scripts there.

Also, have you tried re-downloading lz kernel then flash it? Might be a bad download.

Unfortunately, I have a feeling, with the libc.so error, that it is more of a ROM issue. But since I didn't see the print out of the scripts running in the logcat, there is definitely a flashing/kernel issue. You can also look in /system/bin and try to find the file sh. If it isn't present, then that could be why the scripts aren't running.
[Samsung Galaxy S Blaze 4G] johnb380:
I know the scripts run at the beginning I think that reboot was more like a hot reboot so everything didn't restart Cuz it was already there if that makes sense

And I looked in in it. D and there's 10 scripts present and the bin/sh file is there too and your probably right that it's a ROM issue I would use PA but I don't like the split screen settings is all it probably is a compatability issue with your kernel and Aokp rom but I'm not a Dev I just flash alot lol
[Samsung Galaxy S Blaze 4G] thomas.raines:
Repo updated... Somehow it got broke again so all my commits went out the window... None-the-less, everything is fixed now and I have the latest updates available for building. Sorry I don't have time to build a flashable update. Hopefully I will get a quick chance tomorrow...

Oh, I update branch to jellybean so make sure you update your local_manifest.xml
[Samsung Galaxy S Blaze 4G] johnb380:
Hey Thomas idk why but any of the cm10 or pa or Aokp ROMS I flash this kernel over the vibrate isn't present anymore no haptic feedback at all

I'm not a Dev, I just flash alot.
[Samsung Galaxy S Blaze 4G] thomas.raines:
1: Don't flash LZ kernel over PA... It already has it... And I just checked, I have heptatic feedback and vibration...

2: Logcat...
[Samsung Galaxy S Blaze 4G] thomas.raines:
4.4 is here! Just waiting on download link from goo...

I know there are bugs. CM-11.0 bugs are already known and noted. If you're not sure as to what they are, head over to InkSlinger420 cm-11.0 thread and read about them.

If you find any other bugs let us know. I played with it for sometime, but I can't test everything. I tried to get the unlock code again, and again, tmo refuses to give it to me. Apparently, the guy that sold me the phone didn't pay his final bill and now the phone is blocked. hey want me to give them $400 to unlock the phone... That's what I call a GFY momment...lol
[Samsung Galaxy S Blaze 4G] InkSlinger420:
No eBay unlock codes for ya? Lol
[Samsung Galaxy S Blaze 4G] thomas.raines:
Download links are fixed. Thanks for letting me know...
[Samsung Galaxy S Blaze 4G] tommyboy8125:
The thread to unlock the phone in general works just fine.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I believe he is saying that his imei is blacklisted so he cannot get service to test data and such...
[Samsung Galaxy S Blaze 4G] blazetim:
Hmmm they still are not working for me. They won't start to download then say download failed?
[Samsung Galaxy S Blaze 4G] thomas.raines:
This day is starting out really badly!

I woke up, made coffee, smoked a cigarette, enjoyed a few sips of my awesome coffee (aka army crack coffee as my teenagers call it), hit the power button on the computer and after a few moments, I got an BIOS error message. YOUR HARD DRIVE HAS FAILED!

Thank god for my "Oh crap, just in case, I shouldn't have deleted that file" spare drive! Luckily, I just made a backup 2 days ago, and I can still access the drive via USB. I'm guessing the sector that holds the bootloader is what failed. So, it will become a secondary, by secondary I'm mean for a couple weeks or so (just until I can raise the money for a new hard drive), backup drive, and I'm setting up to use my primary 500gb backup drive.

Didn't know there was one. I will check it out after I get my box up and running again. Thanks...

Now on to the second bad news of the morning. Looks like goo.im shut down to move to the new sever, the files and link got corrupted... Unfortunately, I am unable to do anything about it until I get my box back up and running. So, if any of you guys out there are feeling up to it, please mirror 4.1.2 and 4.4. Thanks in advance!
[Samsung Galaxy S Blaze 4G] ktempleton:
Well look at the bright side at least you still have coffee lol
[Samsung Galaxy S Blaze 4G] lanrrydon:
Question

Can This New Build work on my Pack Man ROM.. Just Curious... I try out the 4.1.2 and 4.1 LOL I also got ma phone crashed...
[Samsung Galaxy S Blaze 4G] njstein:
No. LZ is not compatible with PAC. Dirty Unicorns, Beanstalk, and CM are the only 3 that are.

Sent from a Dirty Unicorn set aBlaze by Lightning
[Samsung Galaxy S Blaze 4G] thomas.raines:
And PA...

Omni and PAC need some work in order to be compatible...
[Samsung Galaxy S Blaze 4G] taodan:
Can anyone mirror the kernel 4.1 cm10.2 or post in on google drive? I could not download it from goo.im. Kept getting message "500 internal error". Thanks
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Custom kernels have a hard time on PAC as they have had to split the frameworks due to so many options involved in the ROM..it would probably be possible (not right now) and I am gonna talk logistics with Thomas this week..just a friendly FYI..:D

---------- Post added at 09:29 PM ---------- Previous post was at 09:28 PM ----------

I believe goo is in the middle of maintainence..
[Samsung Galaxy S Blaze 4G] thomas.raines:
I need to get those commits from you about splitting initramfs... once I get my box back up...

When goo launched the new server, it killed my downloads... Again, once I get my box back up, I'll recompile and upload it again...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Can you compile lz with anykernel?
[Samsung Galaxy S Blaze 4G] Somcom3X:
Looks like it may be carbon too I'm afraid. Maybe it's my device ?

Hope this won't be a problem on 4.4

Well with the huge number of changes to 4.4 code. I'm am going to be spending some time thinking about what my directive would be.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yep...any device, any kernel...my box well be up tonight do I'll teach you how to lz any kernel...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Sounds good man...I was told that lz built with any kernel will work for PAC (just so ya know) as any kernel doesnt care so much about ramdisk and frameworks..
[Samsung Galaxy S Blaze 4G] hailam1991:
kennell is used for stock android 4.0.4?
[Samsung Galaxy S Blaze 4G] Somcom3X:
You've posted in 5 different threads answers that you could have gotten from reading the first post. You've been a member since 2012. I'm pretty sure you've read enough threads explaining the rules.
[Samsung Galaxy S Blaze 4G] goingcrazy614:
Would like in on learning to lz any kernel.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
ok..Let me clarify..

Anykernel is a format..NOT ANY KERNEL...
[Samsung Galaxy S Blaze 4G] goingcrazy614:
My bad. LOL
[Samsung Galaxy S Blaze 4G] njstein:
Thomas, actually got 4.1.2 and 4.4 to download from goo. Did you repost these? Are these okay to flash or should I hold on? I remember you saying that some things got screwed up when goo made some changes and just want to make sure that what I'm flashing isn't corrupted or something!
[Samsung Galaxy S Blaze 4G] thomas.raines:
I didn't re post them... It was the links that got broken. I would think the files are fine... 4.4 was working since I posted it though... But I would wait a bit because I'm going to have a new build for 4.4 here in a bit... it will have the sdcard fix implemented...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Hee Hee...

Yeah, Thomas...Good work with that... ;)
[Samsung Galaxy S Blaze 4G] thomas.raines:
4.4-1 update available

Thanks to [MENTION=5190980]InkSlinger420[/MENTION] @ktempleton [MENTION=837884]carv[/MENTION]sdriver @mikeyman77 @dhacker29 @PlayfulGod and @Skywalker.00

Oh, and SomcomX3...

http://xdaforums.com/member.php?u=4878501http://xdaforums.com/member.php?u=4878501
[Samsung Galaxy S Blaze 4G] njstein:
Ignore what I have deleted. Obviously I can't read instructions properly!!
[Samsung Galaxy S Blaze 4G] nicknc:
So...

For those that encounter a black screen and bootloop after flashing 4.4-1, like me, and can't figure out what the heck is going on-- be aware that the "4.4" part of that file name means CM11, lol-- it's NOT the version of the kernel.

I'm running CM10.2, and this was blowing my mind until I thought things through. Going to give the 4.1.2-CM10.2 version a go now, as that's the right one, I bet. :p
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Yeah..he coulda chosen different version numbers...lol :p just messing Thomas..haha
[Samsung Galaxy S Blaze 4G] nicknc:
Well... it booted, but once inside CM10.2, got android phone FC over and over. Had to wipe system and reflash CM10.2. Yall hit that before? I'm using the latest nightly.
[Samsung Galaxy S Blaze 4G] thomas.raines:
lol... I didn't even realize that... I'm sorry guys... But to be honest, 4.2 and 4.3 versions had bootloop issues so I never released them... I just put 2 and 2 together... I'll fix the changelog...
[Samsung Galaxy S Blaze 4G] nicknc:
Man, I'm completely confused then. So there is no CM10.2 kernel then? What about Blaze_p4.1.2-CM-10.2? I took that to mean it would work on CM10.1 (android 4.1.2) and CM10.2.

Either way, I

didn't

get a bootloop with that one on CM10.2 (latest nightly), but I did get a constant FC for android.phone at the lockscreen.

Thanks for the work, and as a fellow vet, thanks for your service (I saw your retirement announcement a few pages back).
[Samsung Galaxy S Blaze 4G] thomas.raines:
Thank you for your support...

Look at post 2 the changelog... hopefully it will clear things up now...lol
[Samsung Galaxy S Blaze 4G] nicknc:
Yeah, that clears up the confusion for the last two.

So you don't have a kernel for 4.2 or 4.3, right?
[Samsung Galaxy S Blaze 4G] Skywalker.00:
Any of them that say something along the lines of p4-cm-10.2 would be for your 4.3 ROMs. Now, 4.2... I'm not sure :p
[Samsung Galaxy S Blaze 4G] goingcrazy614:
Hey Thomas, you get it working for PAC yet?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Thomas is a bit busy today..and him and I havent had much time to talk about it lately..That is a project upon itself though..As soon as he gets settled in , ill talk to him more about it..
[Samsung Galaxy S Blaze 4G] Skywalker.00:
I wanna get in on this. Anything I can do to help?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Get your build box setup and ready..;)
[Samsung Galaxy S Blaze 4G] nicknc:
Yeah, I tried the latest p4-10.2 one and it wouldn't boot on CM10.2. Maybe it works for you guys down there in Union County, but it ain't working here.
[Samsung Galaxy S Blaze 4G] Skywalker.00:
Maybe it works for some folks down there it doesn't matter where, but I never said it would surely work for you. You asked which one was for cm10.2, and I told you. Simple as that. Tough luck kid.

---------- Post added at 07:56 PM ---------- Previous post was at 07:49 PM ----------

But if it makes you feel any better, I never once had any luck with an lz kernel until 4.4...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
So....

Ok...Look...His naming is a bit confusing but it states what rom they are for right next to em..

Blaze_p4.1.2-CM-10.2.zip

Merged with upstream changes

DO NOT flash this if your ROM dev hasn't synced with Cyanogenmod since 21OCT13, i.e. PA (I'm in the middle of another project with it. I will update it soon.)

Contact your ROM dev if you have any questions.

Blaze_p4.1-cm-10.2.zip

Bumped to p4.1

Added gallimaufry gov

Added lazy gov

Added sio-scheduler

Ideally, I would try the top first..(its in the OP) And it is needed and more functional to flash after full wipe including formatting system..wiping data,cache and dalvic. Flashing rom,then kernel,the gapps..And as far as your little "down in Union County" comment, Its really not needed or necessary. Nobody here gets paid to help you..If you want one on one support i will do it for $10/minute.. Otherwise just take advice and trail and error the process until you get it to work..Because it does..and it is more than likely operator error...
[Samsung Galaxy S Blaze 4G] nicknc:
Wow.

I'm right around the corner from Monroe and meant it light-heartedly :)

Doubtful it's operator error-- I've been flashing for several years, and I feel I'm pretty good at ruling that out. If anything, it's probably a setting that didn't restore well from CM10 (which was on the phone up until a few days ago).

I know there aren't a huge amount of folks with this phone anymore, and from reading back several dozen pages, I didn't notice any similar issues. Hence the report of that particular version of the kernel not working on my particular phone running the latest CM10.2 nightly. Not a big deal-- just a bug report.

I know you're not paid, and am sorry if I conveyed an implication that I expected a level of service beyond volunteer support. That being said, $600/hour is pretty steep....I'm glad you're not charging! :p

---------- Post added at 12:28 AM ---------- Previous post was at 12:25 AM ----------

Doesn't make me feel any better, but no big deal. I had LZ running with CM10 for awhile and miss then battery life. I reckon the best solution is to wait for CM11 nightlies, then.

Enjoy the weather tomorrow-- looks like it's going to be pretty cold for the next week or so!
[Samsung Galaxy S Blaze 4G] njstein:
I must admit, that I tried the p4.1.2 after a clean flash and install and it didn't work for me either. I wish I had been thinking and logcatted it, but I didn't. But, the first LZ for 4.3, p4, works excellently on my Blaze. Give that a shot, see if it works!
[Samsung Galaxy S Blaze 4G] Skywalker.00:
Well look at us, a couple of monroevillians...monroenites... Monroeians? Like I said, with cm11 is the first time I've even been able to boot lz although I've attempted many a times. It's hit or miss I suppose.
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Nick..we are good..the way it sounded was a little hostile, but as it wasn't meant to be..I do apologize..now with the lz kernel..I believe Thomas needs to pull it back in and lower the oc just a little to be fully compatible..back on 4.1.2 with me having the exhilarate..there were 2 versions..one oc'ed at 1.8 and one at 1.5..I tried like hell to get the 1.8 to boot..just black...but the second I tried the 1.5 I never looked back..perfect..it seems the same makes and models of phone are still a little different because the 1.8 worked for a lot of people..just not me and maybe a dozen others..so..needless to say..I'm gonna be talking to him tonight and I'll ask about dropping it to 1.5 and see what happens...:cool:
[Samsung Galaxy S Blaze 4G] thomas.raines:
All that over version numbers!

You guys have to understand a few things:

1- I just retired from the Army

2- I have been spending the last couple weeks packing and preparing to move

3- I finalized everything and moved yesterday

4- On top of my busy schedule, I have been working VERY hard helping inkslinger420 get the sdcard issue fixed.

5- I have been distracted a bit with everything I have going on, hence the fact I didn't properly update the changelog with more info about what version goes with what ROM.

6- I can't fix something when A) you don't tell me that is broken and B) you don't give me a logcat, last_kmsg, or dmesg. Stating that it doesn't boot or it didn't work provides me with NOTHING. How do I know YOU didn't FAHQ it up somehow?

7- This kernel doesn't work with all ROMs anymore. Because so the many differences in some ROMs like PAC, Omni, MIUI, etc, I have to take extra time to compile for those specific ROMs. So if I don't have the extra time, then oh well...

8- Anyone can LZ any kernel. All you have to do is ask, and I will point you in the right direction. It's not that hard.

An last but not least:

When my box went down and goo.im went goofy I asked, more than once, for one of you guys to help me out and mirror them till I got my box back up. NONE of you fell in to help. So if you don't want to help me, WHY THE HELL DO I CONTINUE TO DEVELOP FOR YOU GUYS?!?!?! Because I'm a helluva nice guy that's why.

I spend more time on the blaze and exhilarate than I do my dd and my wife's phone. But I guess since there are so many issues here all because I made a slight goof and not describing something properly for all to understand, then maybe my time on this device has come to an end...
[Samsung Galaxy S Blaze 4G] thomas.raines:
Boy, you guys have missed a lot...

Update is available. Read the changelog for details...
[Samsung Galaxy S Blaze 4G] njstein:
Oooooh YEAH!! Awesome, awesome. I be flashing!

Good to have you back [MENTION=4145127]thomas.raines[/MENTION].
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Well well..lookie who I found in here...:D
[Samsung Galaxy S Blaze 4G] njstein:
[MENTION=4145127]thomas.raines[/MENTION], you are a kernel master and am wondering if you can offer some assistance. On my Tab 2 (I know, wrong device from, but no one there knew much) I'm having a kernel wakelock by the name musb_autosuspend_wake_lock. After many sessions with Mr. Google, I've found crap about how to fix it. It's a doozy, and would like to get rid of it. On 4 hrs it's been tripping my tab for 25 minutes. Do you have any idea on what I can do to lessen it?
[Samsung Galaxy S Blaze 4G] thomas.raines:
Well, first I'm going to flame you for posting this in the wrong thread/forum...

Ok, I'm done...lol

Next, you have 3 options:

1) Send your tab to me as a late birthday present...

2) Hit it with a hammer repeatedly until the wake-lock goes away (usually indicated by several cracks in the screen and a no boot condition)

3) PM me with a logcat and a 24 hr output/dump of BetterBatteryStats.apk (can be found in the play store), and when it is "tripping" your tab, open android terminal emulator and run top -n 1 > / <path to sdcard> /top.log and wait for it to finish. Don't run it on your computer because that could cause another wake lock while it's plugged in.

Also, make sure you PM me with the current ROM/kernel you are using.

As you may have guessed from the mUSB part of it, it has to do with OTG USB connection. I'm thinking a kernel mod might fix it up. Maybe, and this might be a long shot, a simple init.d script might kill it. But again, I need more information.
[Samsung Galaxy S Blaze 4G] njstein:
[MENTION=4145127]thomas.raines[/MENTION] , thanks for getting back on this and a way huge thanks on helping. So I must clarify something, the "tripping" was a wrong way to put that, really wrong and I apologize. What I meant was that the wakelock is keeping my Tab awake. The Tab is perfect otherwise, nothing bad or crazy, just a crappy lock that no one has a clear way to fix. So I'll charge overnight so the battery is full, in the morning I'll unplug and let it sit so BBS has a full 24 hour dump log to output. Do you want the logcat of the whole 24 hrs? I don't mind doing that, really easy, that's just a huge log! Or, since the Tab is running fine just a crappy lock, do you not need the logcat? I'm willing to do and produce what you need to get this fixed! Thanks again!
[Samsung Galaxy S Blaze 4G] thomas.raines:
No, I think BBS will give me what I need... I did some googling after you originally posted this and I have a possible solution, but an output is deffinitely needed so I can see it better...
[Samsung Galaxy S Blaze 4G] NghtWachman:
Downloaded LZ

Wanted to try your work so i can give you a feedback but have not been so lucky with the link you originally provided.

Can you please provide a me am stable link?

Thank you for the awesome job.
[Samsung Galaxy S Blaze 4G] xWolf13:
Haven't been here for awhile lol. But is this compatible with Cyanogenmod 11?
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yes

Update available!
[Samsung Galaxy S Blaze 4G] Traace:
Hi P4.4-4 is booting but got a issue

After 10-20Secs i get a cold boot again...

I also tryed to clear the voltages.

I'm using BeanStalk.