yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] Beastmode:
Re: [Kernel] Lightning Zap Kernel (Updated 23MAR13)

You have to change the file (I believe its an .rle file for blaze) and rebuild the kernel from source. This is, to me, the easiest way because all you need is a tool chain and a terminal lol :P

Or

I think you can unpack the kernel and change the file in the initramfs then repack kernel . this one I'm not 100 on
[Samsung Galaxy S Blaze 4G] thomas.raines:
Like goingcrazy614 said, use Voltage Control app from the market. It is prefered and the code I used in the kernel was specific for that app. There are others like antutu CPU master that work too, but I cannot guarantee which other apps work and which don't since I wrote the code with xan's Voltage Control specifically in mind.

It sounds to me like you aren't giving the kernel a chance. It does say in the OP to let the phone sit for a bit before you playing with it (wait 10 minutes). As for making any changes/tweaks at all, my good friend goingcrazy614 is correct. Do changes in small increments, and give them time to set in. Going to extreme with a value(s), tweaks or other mods can force instability no matter what kernel/ROM you are using. For example, when undervolting, you NEVER want to undervolt a value more than 50mv at a time, and when overvolting, you don't want to go more than 5mv at a time (unless you want to see your cpu LITERALLY explode in your hand).

But, it also sounds like you may be flashing a lot. You might have some pesky gremlins lurking about in your filessytems/partitions. I suggest checking out my Aroma File System Cleaner for the Blaze which can be found in the dev section.

Overall though, I think you are trying to do way too much at once. Slow down a bit.

As for the custom LZ bootsplash, beastmode is correct. You would have to download the source code, change the logo.rle, then recompile the boot.img. As for unpacking and ripping apart the kernel, change the logo.rle in intiramfs, then repack the kernel, good luck. I actually tried doing that on a different device and I never could get the kernel to boot again. That's about the time I decided to build my own kernel...lol
[Samsung Galaxy S Blaze 4G] fasteat1:
i do not want to do that im not that experienced. I understand what u say.

I did leave the kernel to rest for 30 minutes after i flashed the pacman rom. I dont flash alot. also i got it fixed by using blue lightning instead.
[Samsung Galaxy S Blaze 4G] goingcrazy614:
Re: [Kernel] Lightning Zap Kernel (Updated 23MAR13)

Roms contain there own kernel. If you want a different kernel you have to flash it after the ROM. Also, put at least a day between ROM and kernel flashes.
[Samsung Galaxy S Blaze 4G] sttupid90:
um is it normal for it to be stuck on "Thomas. Raines present Lightning zip! Kernel" screen? its been there for about 20mins
[Samsung Galaxy S Blaze 4G] thomas.raines:
Nope... bad flash. Redownload and flash again... make sure you're flashing this on a jb Rom
[Samsung Galaxy S Blaze 4G] DiViNEX:
Hey tom i noticed theres a second build.prop, do i have to merge those lines into the original build.prop or do you have it set so it reads it with the original prop?

★Transmitted from the AC!DIC planet Blaze, sector AOKP, using Lightning Zap tech within the Samsung Galaxy★
[Samsung Galaxy S Blaze 4G] thomas.raines:
It's actually build.prop2... rename it to build.prop(2) with root browser, then reboot...
[Samsung Galaxy S Blaze 4G] DiViNEX:
Maybe i should of been more specific...What i was trying to ask is if build.prop(2) loads up alongside build.prop, or do i have to take the tweaks from build.prop(2) and put them into build.prop. Ive never seen 2 build.props until i started using your kernel, thats why im asking lol

★Transmitted from the AC!DIC planet Blaze, sector AOKP, using Lightning Zap tech within the Samsung Galaxy★
[Samsung Galaxy S Blaze 4G] thomas.raines:
Ah...gotcha... You don't need to do anything... I'm trying different methods to implementing the build.prop tweaks without actually adding them to the build.prop. I think the best approach was when I added them to the default.prop though... I'm still testing another approach though...
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Any luck with intellidemand?
[Samsung Galaxy S Blaze 4G] thomas.raines:
Kinda shifted my focus away from it... gonna hit it back up though...probably tonight or tomorrow...
[Samsung Galaxy S Blaze 4G] njstein:
Awesome Thomas! Newest version installed and running like a charm. As always your work with the Blaze is unparalleled!

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] njstein:
Have a few questions: read in one of the posts to give a day in between flashing a ROM and new kernel. I did not, should I do a complete wipe and do this? I'm running the most recent PA, and the kernel is version 3.0.49. 3.2, whereas the newest kernel version seems to be above this (in my noob mind). Is this newest kernel above the version in PA?

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] thomas.raines:
No you don't. Although good advise, I never wait.

Unfortunately, my kernel version isn't displaying correctly. It's one of those things I started working on, but got side tracked and moved on to better things...lol... It's something that I am currently revisiting though and hope to have it fixed in the next update or so...

But for now, the best way to know is by reading the changelogs in my PA thread (I will post there if I have included a kernel update) and .zip name, i.e. Blaze_p3.*.zip.

If you are still unsure, don't hesitate to ask me.
[Samsung Galaxy S Blaze 4G] njstein:
I ask because I'm running newest PA, flashed this kernel, and now getting a lot of random reboots. Bad flash? Bad download? I wiped everything, black hole and killed the Gremlins. Any thoughts?

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] DiViNEX:
As tom has said before if you download the zip with your phone it could have a bit or 2 that's corrupt or missing that will cause issues. Download all roms, mods, kernels, from your computer and transfer to the sdcard and flash again you should have a better experience.

★Transmitted from the AC!DIC planet Blaze, sector AOKP, using Lightning Zap tech within the Samsung Galaxy★
[Samsung Galaxy S Blaze 4G] thomas.raines:
Bad finding cuz my blaze has been on for nearly 2 weeks straight with no random reboots...same kernel, same Rom...
[Samsung Galaxy S Blaze 4G] anactoraaron:
I was having that issue also but all is well on 3.5.1 LZ. Maybe try to reflash LZ?

I don't know if you are aware Thomas, but with 3.5.1 my screen lock sound is delayed and sometimes is doesn't make the sound until I press the power button to turn the screen back on. Nothing major.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Fully aware of it thanks. I actually am testing the fix/update as we speak...

I'm working on another project tonight while I test and will have the update uploaded tomorrow morning...

It was also presenting a problem with receiving texts in a timely manner and causing multiple texts to be received and sent...
[Samsung Galaxy S Blaze 4G] njstein:
Reflashed through computer, still had reboots. Do you flash through the internal, or external SD? Does it matter? Would like to find the problem because my Blaze runs fantastic through this kernel version when it works . Would a logcat help?

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] Beastmode:
Logs always help :)

And idk about having to download through the PC rather than phone. I've downloaded all my updates for my personal phone thru my phone and I've yet to get a bad full download.

As for flashing from internal or external it doesn't matter. So long as the file is correct and it flashes ok then you're set. If you're still having issues grab some logs as it might be some apps causing instability or the kernel has some.
[Samsung Galaxy S Blaze 4G] thomas.raines:
I've had several downloads go array when using my phone... depends on how good/bad your network coverage is I guess...lol

But yeah, at this point I need some logs...
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Tried to download Blaze_p3.5.1.zip - file not found. Can someone please reupload? thanks
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yeah, I accidentally deleted it... I'm uploading p3.6 tonight though so just be patient guys...
[Samsung Galaxy S Blaze 4G] njstein:
Clarification

Thomas, so I haven't had time to research how to do a logcat, so I'm trying to fix the reboot issue through the build.prop option but I when I look through the pa zip I can't find the lightning zap in the build.prop or through Root browser in my systems. Any suggestions as to where I need to look to find this? Thank you!
[Samsung Galaxy S Blaze 4G] xWolf13:
On the change log. New version says 3.5.. Isn't it 3.6? lol :p

Sent from my Nexus 5 with Key Lime Orange Mango Beef Tuna Pie
[Samsung Galaxy S Blaze 4G] thomas.raines:
Updated 15MAR13

3.6 is up

Read the changelog

I'm calling EOL on this kernel for now.

I'm closing this project for now so I can dedicate my time to merging to cm10-1
[Samsung Galaxy S Blaze 4G] thomas.raines:
Fixed... thanks
[Samsung Galaxy S Blaze 4G] Jserrano56:
Wait... Updated March 15th? Did I Completely Misunderstand The Last Few Post Was There An Update Today Or Not?
[Samsung Galaxy S Blaze 4G] thomas.raines:
I was tired...lol

There is an update...I'll fix it so nobody is confused...
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Does the updated version have the newest version of LZ? Or still blue lightning? Not sure if I still need to flash LZ over it. Thanks!
[Samsung Galaxy S Blaze 4G] thomas.raines:
Check you threads homie. This is the Lightning Zap! kernel thread...
[Samsung Galaxy S Blaze 4G] xWolf13:
This is lightning zap. Not Blue Lightning. 3.6 is the newest and latest version of LZ.

Sent from my Nexus 5 with Key Lime Orange Mango Beef Tuna Pie
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Ahh sorry! I thought this was the AOKP ROM thread. wasnt sure if that ROM now came with LZ rather than blue lighting now. gahhhhhh!
[Samsung Galaxy S Blaze 4G] woodyjlw:
I wiped today to try cm10 latest with the 3.6 lz and have ran smooth all day with good battery and have not gotten any multiple text all day! Also I used the aroma FSC and ran it several times in a row just to see if it would give me the same trouble it did the very first time I ran it and I can not get it to freeze up on me so i assume all the gremlins are gone. oh and you also fixed me on usb storage with ubuntu! I can now use ubuntu to transfer files back and forth on both sd cards without the phone freezing up. very happy with results!

many thanks! :good:
[Samsung Galaxy S Blaze 4G] njstein:
New build works like a champ! Got rid of an app that I think might have been causing my random reboots and tweaked some settings. Fantastic work Thomas!

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] thomas.raines:
What app?
[Samsung Galaxy S Blaze 4G] njstein:
JuiceDefender. I installed the new build with JuiceDefender, random reboots. Without JuiceDefender, no more reboots. The only other thing I did was delete a few cpu profiles in ROM Toolbox.

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] thomas.raines:
Juice defender isn't recommended...lol

Beside, now that I got the internal app killer working right, it's not needed... just go to settings/developer options and check the option to kill an app when you hold the back button and the option to destroy a process when you leave it... just don't long press the back button on calendar or desk clock(alarm) cuz it will kill it and you won't get your alarms/alerts...
[Samsung Galaxy S Blaze 4G] njstein:
I've come to the conclusion that JuiceDefender isn't that effective. It might do a little something-something, but every since uninstalling it, I haven't seen any difference. I'll try the app kill, sounds like a good option. I run Greenify, is app kill similar or something different?
[Samsung Galaxy S Blaze 4G] henslo:
If you are looking for better battery life there's no need for apps like juice defender, greenify etc. IMO they are worthless intrusive and do more harm than good. Check out this thread http://xdaforums.com/showthread.php?t=1827676
[Samsung Galaxy S Blaze 4G] njstein:
Thanks for the link!! Insanely insightful. Will spend a lot of time going through all that to pin down my battery. I've had my suspicions about JuiceDefender, glad to see they were right. I use Greenify to stop background apps that shouldn't be running (i.e. Facebook). But after reading that thread, most of those background apps will be removed! Now Greenify is on my turd-list, might be the next to go! Thanks again.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Again, set the hold back button to kill an app and don't keep activities in developer options, and you will be set.
[Samsung Galaxy S Blaze 4G] Beastmode:
Wouldn't he lose the ability to multi task if he does this?

Idk about the user but I don't like it when my browser or a few other apps close and don't load from where I left it.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yep

I agree with some things. But to every pro there is a con. Basically, it's performance over battery or battery over performance.

On the flip side, if you don't want to complete kill a particular app, then don't long press the back button when you exit it. Just tap it. Then the process won't be destroyed.
[Samsung Galaxy S Blaze 4G] Beastmode:
You mentioned to turn on the don't keep activity's that destroys the activity even without the back button
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yep, keep the 2 together... Seems to work best that way... at least for me...
[Samsung Galaxy S Blaze 4G] Beastmode:
Lmao that's not what I mean...heres my thing

if you turn on the don't keep activities then they are destroyed once you exit.

you said if they turn it on they won't be destroyed if u just press the back button but not the hold back to kill

lol but if working correctly once you turn on the Don't keep activities then all activities are destroyed no matter if u press back or hold back to kill lol that's what I meant lol
[Samsung Galaxy S Blaze 4G] thomas.raines:
I gotcha, and you would think, but it doesn't... only triggers to destroy the PID when you kill the app. It looks to me like it's something in the ROM.
[Samsung Galaxy S Blaze 4G] njstein:
Got rid of Greenify and took your advice. Working great, battery life is better than ever. Now going through the wakelocks and trying to get rid of those. Thanks again thomas!
[Samsung Galaxy S Blaze 4G] demonsavatar:
I didn't see it mentioned so I'll ask. Does this kernel do BLNWW (back light notification without wakelock)? I noticed on CM10 that is my major wakelock.

If it doesn't support it, may I request the feature?
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Flashed this and aokp this weekend and my alarm didn't go off this morning. When I went to check the phone, the screen lit up and then it went off right when i woke it up
[Samsung Galaxy S Blaze 4G] thomas.raines:
I'm not sure about that... Remind me after I finish the merge to cm-10.1 and I'll look into it.

You cannot use the long press back button to kill desk clock after setting your alarm. The internal app killer is working too well...lol

To work around this, after setting your alarm, just short press/tab the back button to exit and you should be fine; however, if you still have issues let me know. I'm no going to be too concerned with this because I'm working on merging to cm-10.1 now. If it is still a problem after the merge, I will definitely be fixing it.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Update available

Read the changelog

This is jellybean final. I'm am now in the process of merging to cm-10.1!
[Samsung Galaxy S Blaze 4G] ktempleton:
Did you guys get 10.1 working then
[Samsung Galaxy S Blaze 4G] thomas.raines:
Read the op closer... in STARTING the merge to cm10.1... I haven't even but anything yet... I'm still syncing...
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
I just tried setting it again and didn't kill the app. Still had the same issue this morning. Alarm set for 7 and i wondered why time it was. Checked the screen and 7;10 the alarm starts going off cuz the screen was turned on
[Samsung Galaxy S Blaze 4G] thomas.raines:
Ok...when I get to my computer, I'll post a better work around...
[Samsung Galaxy S Blaze 4G] ducky69247:
Flashed this to my Blaze running Provision rom, constantly crashes (I mean right after boot, EVERY time...) and will not allow recovery mode (not via rom manager, not via adb reboot, not via inbuilt provision reboot function, not even via power/volume button combo), so I can't even restore the nandroid I took right before flashing it. -.-

Advices?
[Samsung Galaxy S Blaze 4G] anactoraaron:
...try 3.6 and not 3.6.1...? It may help. I don't know about everyone else but I always full wipe before restoring a nandroid.
[Samsung Galaxy S Blaze 4G] ducky69247:
Attempting odin stock rom reflash.. I can't restore without recovery >.<
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Thanks! I'm down to having someone call me every morning
[Samsung Galaxy S Blaze 4G] taodan:
I am on the same boat too. Can't not boot into recovery at all.
[Samsung Galaxy S Blaze 4G] ducky69247:
I ended up using {OOPS!} Quick Recovery and then flashing Provision Rom (the one I was using that I tried to apply LZ! kernel to)

Up and running, more or less just as functional as before
[Samsung Galaxy S Blaze 4G] taodan:
Thank you for the tip, sir! Couldn't believe the latest version caused such a problem.
[Samsung Galaxy S Blaze 4G] thomas.raines:
For the instability issues. It looks like it's gremlins again...

I'm not sure why this is happening. I had the same issue, I pushed a fresh copy of 3.6.1 to my sdcard, made a backup with titanium pro, did a complete wipe with FSC (no backup option), flashed the ROM and LZ kernel, restored my apps and data ONLY (no system data) and all is fine.

For those of you with no sound on calls, again, I had this issue but it was fixed when I performed the above.

For the alarm issue. I still can't pinpoint it, but I found a good workaround:

Under developer options in setting check the box for the "Stay Awake" option. This will not allow the phone to sleep while it's plugged in. Open deskclock from the app drawer. Now, you can dim the screen by tapping on it, or you can long press it and it will display the deskclock screensaver. Set the phone down and enjoy a good night sleep and be awakened by your alarm. I would suggest testing this a couple times to ensure it works for you.
[Samsung Galaxy S Blaze 4G] njstein:
Thomas, I'm assuming to correctly install the newest version of this kernel is to follow the instructions for 3.6? As in go into init.d and replace the kernel info after flash?

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] anactoraaron:
I decided to try out the T989 radio (UVMC6) this morning after reading about it either here of another thread. Afterwards I wiped davlik and rebooted. I no longer: get duplicate text messages, there's no longer a delay to hear the screen lock sound, bln is no longer delayed, and everything in general seems to be more responsive... strange... Just wanted to post it here in case anyone is experiencing random issues/gremlinyness (lol). Maybe try flashing the UVMC6 radio for the T989 from here, or re-flash the UVMB1 and test it out.

Is it possible that the gremlins/issues some of us have experienced came from a bad modem/radio flash?
[Samsung Galaxy S Blaze 4G] DiViNEX:
I flashed 3.6.1 yesterday and now everytime someone calls me or if i make a call both sides hear nothing...

Logcat: http://db.tt/ZeWIlvsE

★Transmitted from the AC!DIC planet Blaze, sector AOKP, using Lightning Zap tech within the Samsung Galaxy★
[Samsung Galaxy S Blaze 4G] njstein:
Mi

You said that you flashed UVMC6 but the link says UVMC4. Is there a difference? Or am I wrong on those builds?

Sent from ParanoidAndroid Blaze using xda Premium

---------- Post added at 04:24 PM ---------- Previous post was at 04:16 PM ----------

Nevermind. I see it now. Boy, i feel stupid.

Sent from ParanoidAndroid Blaze using xda Premium
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yep

Go 2 posts up from yours... can try flashing modem too...not sure if it will fix it, but it's definitely gremlins somewhere...
[Samsung Galaxy S Blaze 4G] ducky69247:
Got antsy and after my clean rom flash from yesterday I flashed 3.6.1 again. An hour later and it seems stable so far... Wish me luck, Provision's kernel was just eating up my battery life, and this seems like just what I need
[Samsung Galaxy S Blaze 4G] Beastmode:
Tbh I don't buy into "gremlins" at all. I think things can go wrong if someone restored data and then issues come.

A bad modem flash could be it but to that many people I doubt unless the script isn't flashing right but again doubtful.

Can't people with the issue flash another kernel to check? If it's a modem issue then flashing one would fix it and is quick to check.

just my ideas and my own research I provide.
[Samsung Galaxy S Blaze 4G] flyers00:
I'm not sure how or why issues occur like this but if anyone would have issues with "gremlins" I would be a likely candidate. I have been rooted, flashing test ROMs, kernels,etc. Since the days of dknight .

I'm currently running cm10 nightly,using stock kernel at the moment . I'm averaging 14 hrs on a charge. WiFi on,email,text,Bluetooth enabled.

When I'm flashing a new ROM I'm wiping cache ,data and formatting system. After I'm done doing this, I flash ROM,gapps,etc and I'm good to go.

At some point someone should put together instructions on how to do this and see what happens. I appreciate all the work being done. I look forward to the day we see cm10.1 on the blaze.

If anyone needs help testing ,give me a shout. Keep up the good work
[Samsung Galaxy S Blaze 4G] DiViNEX:
Lazy me lol

★Transmitted from the AC!DIC planet Blaze, sector AOKP, using Lightning Zap tech within the Samsung Galaxy★
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Still having issues with the alarm. Made sure I didn't kill the app after setting it

---------- Post added at 07:48 AM ---------- Previous post was at 06:49 AM ----------

I'm also getting duplicate texts everytime someone texts me. Not sure if that's the aokp rom or the kernel. The screen also does turn on when I'm getting a popup sms. I know it's not the app. I have to press the power button for them to show
[Samsung Galaxy S Blaze 4G] thomas.raines:
The stability of this latest update really has me concerned. I rebooted my phone this morning just to go back to the no sound with calls issue. I'm going to backtrack this evening and see if I can locate what went wrong. Bare with me guys...I'll get it fixed...
[Samsung Galaxy S Blaze 4G] henslo:
After flashing and using the T989 radio for a few days, the no sound in calls, duplicate/ late texts have went away. Getting better signal also, at work all I get is edge now have h+ in more areas.

Maybe try testing and see if its modem or kernel related? Others are seeing improvements with the 989 radio also.

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] ducky69247:
I found my gremlins again too, after trying to boot into recovery and again finding I couldn't (LZ! is clearly removing it) I tried to add it again using the Rom manager app, and reboot into it, and again it refused to enter recovery mode, instead booting normally and being unstable, crashing to power off every time the launcher loads. I have to pull the battery each time to turn it back on.

Trying another kernel to see if I still get the instabilities after doing different things
[Samsung Galaxy S Blaze 4G] chjema:
I'm using the latest LZ, and yup...recovery is long gone.

Flashing a new recovery from ROM manager brings it back.
[Samsung Galaxy S Blaze 4G] DiViNEX:
Which radio? Link please?

★Transmitted from the AC!DIC planet Blaze, sector AOKP, using Lightning Zap tech within the Samsung Galaxy★
[Samsung Galaxy S Blaze 4G] chjema:
http://goo.im/devs/Void_Dweller/SGH-T989D_TLMC4_radio.zip