yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] :
Research my friend (:

http://www.droidxforums.com/forum/droid-x-hacking-guides/15053-undervolting-guide.html
[Samsung Epic 4G Touch] ps3hacker3:
One step at a time no one knows what you chip is capable of trial and error is the best way to go about it really
[Samsung Epic 4G Touch] :
I can confirm that flashing new kernel bootloops on WFTN.
[Samsung Epic 4G Touch] ktempleton:
Logcats

Dmesg
[Samsung Epic 4G Touch] t0mmyr:
I take it this is still cm10 only? And won't work on cm9 ics?
[Samsung Epic 4G Touch] thomas.raines:
You got it... I don't go backwards...lol

I'm working in a tutorial on how to dev yourself... once in done, you can follow the guide and make a cm9 lz yourself
[Samsung Epic 4G Touch] eigokyoukan:
Did you ever get this to boot? We are having the same issue over on PACman. I tried every version since thr 4412 switch over and it just won't boot.
[Samsung Epic 4G Touch] tonwarr.the.incredible:
Phase 4 works flawlessly with Dirty Unicorns. Not even a hiccup since I've flashed it. :D
[Samsung Epic 4G Touch] beezie42:
We just have to wait for all the developers to upgrade there kernel source. Some have already. I'm only able to use this kernel on Revolt, slim, and dirty unicorns at the moment.

It's working awesome on revolt, loving the overclock. :beer:
[Samsung Epic 4G Touch] Kevin cracolici:
Same with slim bean
[Samsung Epic 4G Touch] eigokyoukan:
That's the thing. Pacman is already on 4412. Been waiting on lz to do same. So slim bean, Revolt, and DU working fine... Looks like pacman and wftn having issues... OK imma look at what version of cm and aosp sources these roms are using.
[Samsung Epic 4G Touch] deaver_92:
I use Exit_Only's tweak package so a reflash was in order to eliminate that as a possible cause for error.

As far as kernel updating goes, I thought everyone was pulling from Dastin's repo? If that's the case wouldn't Dastin have the most up to date kernel?

I will attempt a logcat and dmesg tonight when I get home. Never done either on boot (only while phone is on) so if I get it wrong don't shoot me. :D
[Samsung Epic 4G Touch] bcparker:
Anyone try this with smartassv2 yet? I've been using pegasusq with the old and new one and I'm curious which will give me better battery life.
[Samsung Epic 4G Touch] eigokyoukan:
http://xdaforums.com/showthread.php?t=1736168

It's going to depend on how you use your phone. Learn what the governors do, then make a choice based on how you use your phone. It's all going to be highly subjective to usage.
[Samsung Epic 4G Touch] :
Well, I lost my logcat. >.>

I'm not home so I can't run a logcat.

But here's the Dmesg i think: http://pastebin.com/fRmjtyVg
[Samsung Epic 4G Touch] kchannel9:
How can I determine if Vanilla Rootbox has the correct kernel to be compatible with the recent update?

sent from my GS2/ET4G (AOKP/CM Rootbox 3.9.1 20130613) on Xparent Tapatalk2
[Samsung Epic 4G Touch] eigokyoukan:
Ask the dev? Seriously they should have said something recently if they did switch over.

Or you could make a nandroid and flash and check. If you boot congrats! If not then restore and wait for support :D
[Samsung Epic 4G Touch] Warboy:
Glad to see the kernel is at p4, Does it work with GPU overclocking yet using Extweaks? since you did use some snippets from Agat's Kernel?
[Samsung Epic 4G Touch] thedarksavant:
I got a logcat, but logcat seems to quit in the middle.

I'm not sure if this has the error or not.

Edit: This is with PacMan

Edit: Added another logcat with a fatal error

Edit: Although I did see this:

E/dalvikvm( 2399): Could not stat dex cache directory '/cache/dalvik-cache': No such file or directory

I/dalvikvm( 2399): Unable to open or create cache for /system/framework/apache-xml.jar (/cache/dalvik-cache/system@framework@apache-xml.jar@classes.dex)

D/dalvikvm( 2399): Unable to process classpath element '/system/framework/apache-xml.jar'

E/dalvikvm( 2399): No valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar'

E/dalvikvm( 2399): VM aborting
[Samsung Epic 4G Touch] CwbAnDroidCwB:
Everything seems to be great on thinking bridge
[Samsung Epic 4G Touch] thomas.raines:
I think that was part of the commit I cherry-picked... try it and see

Notice all that points to dalvik?

Try wiping /cache and dalvik cache from recovery, then reboot, if that doesn't work, wipe /system /cache and dalvik cache, reinstall ROM, gapps, kernel

But I think your real problem is here:

I/ServiceManager( 1801): service 'media.audio_policy' died
I/ServiceManager( 1801): service 'media.audio_flinger' died
I/ServiceManager( 1801): service 'media.player' died
I/ServiceManager( 1801): service 'media.camera' died

Which is part of surfaceflinger crashing. I would go with a fresh install. Also make sure the DEV of your ROM has updated the ROM to use the smdk4412 kernel...
[Samsung Epic 4G Touch] eigokyoukan:
Pacman has been on 4412 for at least a week. I had already tried all that you suggest before.

Recovery

Factory wipe

/format system

Install rom

Install kernel

Nothing...

I also tried a fresh install, reboot to let rom settle, back to recovery, wipe dalvik and cache then flash p4. Still nothing.

I'm looking into what version of cm and aosp sources the non working roms are using compared to working ones now. For all intents the kernel is working fine. It's the roms not being happy with them.
[Samsung Epic 4G Touch] zimlokks:
same happens with WFTN as it can't create the dalvik-cache, i rebooted back into recovery and flashed my old kernel and it started building the dalvik-cache.
[Samsung Epic 4G Touch] thomas.raines:
I did a complete wipe because I had the same issue... but I might need to sync something upstream like the device files... I'm thinking possibly a mount or perms issue at this point... have you tried fixing perms after flash?
[Samsung Epic 4G Touch] ktempleton:
Hey Thomas have you seen what I've been sending you and posting in your other threads
[Samsung Epic 4G Touch] eigokyoukan:
Let me try this. Will report back soon.
[Samsung Epic 4G Touch] Warboy:
Does not work with ExTweaks at all.
[Samsung Epic 4G Touch] eigokyoukan:
Fixing perms on a non working ROM was a no go. The kernel definitely works though! I am on DU now with it. So weird because for all intents... all the ROMs, working or not, are on the same CM base (10.1.1 RC0).
[Samsung Epic 4G Touch] sader2202:
From what I can read, this doesn't work with pacman.

Hallowed Is The Sader
[Samsung Epic 4G Touch] eigokyoukan:
I can confirm that. Its something I'm working on troubleshooting ATM.
[Samsung Epic 4G Touch] zimlokks:
got it working, it somewhere between it cant mount cache or cant start building dalvik-cache, i just flashed the kernel manually not wiping cache nd it flashed flawlessly
[Samsung Epic 4G Touch] jwhyte:
What ROM?
[Samsung Epic 4G Touch] zimlokks:
WFTN not the latest version since my isp sucks and i have no service
[Samsung Epic 4G Touch] thedarksavant:
How does one do that? Doesn't the kernel install script format cache?
[Samsung Epic 4G Touch] deaver_92:
Yup. I was wondering the same thing.
[Samsung Epic 4G Touch] elport:
Hey KT and tr I just flashed 1.1 over 1 and gapps didn't delete
[Samsung Epic 4G Touch] paranoid android85:
Same here
[Samsung Epic 4G Touch] dasesq:
Installed 1.1 directly over cm10.1. Still have gapps
[Samsung Epic 4G Touch] btoddweber:
Ditto on b stalkk
[Samsung Epic 4G Touch] dastin1015:
Most likely, but may not be, due to the fact that the ROM dev hasn't properly kept up to date with keeping kernel and user space libs up to date with my repos since this kernel is a fork of my cm-10.1 kernel. Grab the libakm.so from my ROM to fix rotation and the sensors.smdk4210.so to fix compass with this kernel since it uses my latest code.

私のEVO 4G LTEから送信される。
[Samsung Epic 4G Touch] t0mmyr:
was i supposed to see lightning when it restarted? cuz i just did

---------- Post added 9th May 2013 at 12:02 AM ---------- Previous post was 8th May 2013 at 11:57 PM ----------

did u modify any of the values or left it stock after flashing?
[Samsung Epic 4G Touch] t0mmyr:
Successful flash on unofficial bbb9 Rom. Gapps remained untouched and functional.no problems with rotation.

With disregard to ops instruction to wait 10 minutes I ran before and after benchmarks to see if there were any immediate changes visible:
[Samsung Epic 4G Touch] t0mmyr:
I think this killed my root. Feels like I need to flash something to gain root again
[Samsung Epic 4G Touch] ktempleton:
In twrp it ask you if you want to restore permissions for the su binary so try fixing permissions
[Samsung Epic 4G Touch] cephaus:
Flashed 1.1 on slim bean, gapps intact, didn't need to reflash , everything seems to be in working order so far.
[Samsung Epic 4G Touch] elport:
This kernel is pretty sick. No problem to report on this end.
[Samsung Epic 4G Touch] hlxanthus:
Just flashed this into WFTN cm10.1 and will let you know how it goes. I am curious though why you are including the whole boot.IMG and not just injecting the kernel into it. Perhaps it is a device specific thing, as I am new to this device (previously on nexus devices) or perhaps you did other mods in there as well besides the kernel. I could do without root browser included (many aosp ROMs have their own file manager) and while I like the boot animation (pretty slick really) it might not be for everyone. Anyway, everything is running very nice so far and I will give an update on performance and battery life soon.
[Samsung Epic 4G Touch] mastamindz:
So If I were to use this kernel for my S2 us cellular phone should I still need to run the converter that we use to make our phones to work on sprint after I flash kernel. That is if y'all are familiar with our converter we use.
[Samsung Epic 4G Touch] thomas.raines:
Wow, so many posts over night, I can't comment on all of them...lol

Glad you guys are liking it.

First off though, thanks to dastin1015 and Team-Hydra for the source. I apologize for not including your guys in the OP.

As for the benchmarks, keep in mind that they are only a reference point. But, if you want to raise your benchmarks, change the up_threshold to 15 in the governor script. You could also consider changing the io-scheduler and governor.

As for other tweak packages/apps, I would not suggest using them as you could cause conflicts. With that said, if you do not like my default values and have found your values with a particular tweak has better results, let me know and I'll look into it.

As for why am I including the boot.img?

The boot.img consists of several parts, which either now have or will have mods to it. Things like /proc, /sys, the kernel, ramdisk and root partitions to name a few. Lightning Zap! kernel vision is not to be artificially injected into a kernel or ROM, but to be written directly into to. Although tweaks, scripts, etc that are injected into it work, I have found that by writing them into the kernel and ditching the scripts provides better results.

If you don't like something that I included like the bootanimation or root browser, then simply remove/replace it. I dev for the general population and not to individual wants/needs; however, suggestions are always welcome and considered. I learn more from what you tell me with your experience than I can from playing with the device. Mainly because, everyone uses their phone differently.

Again, I am happy you guys are enjoying this kernel.
[Samsung Epic 4G Touch] hlxanthus:
Ahh . . so the scope here is beyond a kernel, but rather performance enhancement built around your kernel! Excellent. I look forward to seeing how this progresses
[Samsung Epic 4G Touch] Takers_ats:
Has anyone that has tested this kernel seen the low speaker volume issue?
[Samsung Epic 4G Touch] daddyodizzel:
My sd card unmounted by itself. Though nothing a little reboot couldn't fix.
[Samsung Epic 4G Touch] elport:
Nope speaker sounds fine. When are you experiencing this?
[Samsung Epic 4G Touch] Takers_ats:
It was a circulating bug in cm10.1 that kept me from running aosp roms since I listen to Slacker all the time. I think I will try Quattro with this kernel
[Samsung Epic 4G Touch] elport:
That bug hasn't been around with KT.

Be careful with running anything else with this kernel. If you have any issues you be advised to wipe and clean install
[Samsung Epic 4G Touch] thedarksavant:
Well, here's one way, but I don't think it gets past the cache format:

http://www.youtube.com/watch?v=k7kHKeJEtuY

---------- Post added at 10:21 AM ---------- Previous post was at 09:32 AM ----------

Based on zimlokks' success, I hacked the update scrip to not format cache and got the kernel to boot on the 7/3 version of PACMan.

Here's a link to my hacked zip: https://www.dropbox.com/s/xdfbujv5gl5ewos/smdk4412_p4_no_cache_format.zip

What I did:

1. factory reset

2. format cache

3. flash PACMan

4. flash GAPPS

5. reboot

6. after boot, reboot to recovery

7. flash my zip

Please try at your own risk.
[Samsung Epic 4G Touch] zimlokks:
i just installed it using flash_image when the OS is running, since i had to inject twrp i did it based on that, i injected it(twrp that is) and then flashed it doing flash_image /dev/block/mmcblk0p5 /tmp/new.img... after it flashed i rebooted and then rebooted bak into recovery and wiped dalvik-cache and it worked but of course i did backup all the device since i was afraid of not being able to boot

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] sader2202:
Working

Hallowed Is The Sader
[Samsung Epic 4G Touch] jwhyte:
+1

Md5

fc4799fefd6578bfac8c7955689a191c

For anyone wanting to check download.
[Samsung Epic 4G Touch] deaver_92:
Installed...booted...excited!! Yay overclock!

Sent from my E4GT on WFTN
[Samsung Epic 4G Touch] jwhyte:
Anyone have details on hypervtnt governor? T.raines posted that there were going to be tweaks for that gov. All I saw was for the on demand gov.
[Samsung Epic 4G Touch] zimlokks:
i believe its just a modified hyper governor, using setcpu u can modify some of its parameters

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] deaver_92:
Cpu and voltage settings didn't stick through reboot.
[Samsung Epic 4G Touch] jwhyte:
Did you use the voltage control app? That works for me after you set it as default settings then select set as set on boot.
[Samsung Epic 4G Touch] zimlokks:
i set it to use init.d or use setcpu since its nicer

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] jwhyte:
I set it on boot not the init.d it gives me a countdown after boot until it's set.
[Samsung Epic 4G Touch] sader2202:
Anyone running 1.6 GHz stable?

Hallowed Is The Sader
[Samsung Epic 4G Touch] ps3hacker3:
Yep by raising the MV at 1.6ghz by 25
[Samsung Epic 4G Touch] beezie42:
Maybe I'm just lucky but I have had no issues on 1.6 ghz stable. Battery life with it overclocked is still great.
[Samsung Epic 4G Touch] diceman1000:
Working on Domination without issue so far

---------- Post added at 06:46 PM ---------- Previous post was at 06:02 PM ----------

Can I flash TWRP with this kernel?
[Samsung Epic 4G Touch] deaver_92:
Didn't realize there was a set at boot setting. It stuck through boot this time.

I'm stable at 100mhz min, 1600mhz max w/ cfq and ondemand. Haven't run any cpu intensive apps yet though.
[Samsung Epic 4G Touch] jwhyte:
Follow up to my post on pacman. If you are using the lightning zap kernel with the script edits for cache from thedarksavant be advised if you wipe cache's even after it had been installed you will boot loop. So make sure to check anything you flash and have a nandroid.
[Samsung Epic 4G Touch] eigokyoukan:
I've been using it for a day so far and it gives me battery life similar to Pegasusq but feels a bit snappier.

I had one freeze running at 1.6 but to be honest I'm am 99 percent sure it was the app I was testing since I've been clear since it was removed.
[Samsung Epic 4G Touch] diceman1000:
TWRP is OK no?
[Samsung Epic 4G Touch] thedarksavant:
Just to be clear, I have not changed the kernel, just the update script. It's still the lz kernel through and through.
[Samsung Epic 4G Touch] thomas.raines:
I tried to dl your modded script to see what it is you done, but the dl failed because the rain keeps knocking out my power . So I'll just ask here. Did you remove both the dalvik wipe and /cache wipe?

Instead of modding the script to try and work around, can someone pull me a pruned dmesg log?

Boot to recovery, plug into computer & start adb shell then type:

dmesg|grep err
dmesg|grep fail

and let me know if anything turns up on that...
[Samsung Epic 4G Touch] thedarksavant:
Yes, when I learned it was the cache building that crashes the VM, I removed the recursive format.

It boots, but you can never clear cache again, so not a solution.

I keep trying to stress it's a hack.
[Samsung Epic 4G Touch] jwhyte:
Edited for clarity. Thanks.

---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------

Edited.
[Samsung Epic 4G Touch] thedarksavant:
I just don't want any undue credit :)
[Samsung Epic 4G Touch] jwhyte:
No problem I'm just glad to have a temporary hack. Switched from PAC just to run it until you posted this. Thanks to [MENTION=4145127]thomas.raines[/MENTION] for an amazing kernel!
[Samsung Epic 4G Touch] thomas.raines:
I understand that it's a hack/workaround and not a fix. And I really appreciate that you figured it out. But now we need to find the real problem so I can find a solution. I know it's crashing the dalvikvm. It's also happening only on certain ROMs, so I'm thinking it lies in the build.prop between one of these entries:

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
dalvik.vm.lockprof.threshold=500

I pulled these from slimbean, which what I'm running atm.

You guys that are running PAC and WFTN (so far the only 2 I'm tracking with this issue), might want to compare these values in your build.prop and adjust yours to match those I just posted. Then install lz kernel and see if it works. If this is the case, then I can simply write a script that will changes which ever value. Resulting in problem solved. But the fix would be to talk to that ROM dev and encourage him/her to change it in their source which would result in problem fixed...
[Samsung Epic 4G Touch] deaver_92:
I have all the same values on WFTN.
[Samsung Epic 4G Touch] jwhyte:
Same for PAC.
[Samsung Epic 4G Touch] eigokyoukan:
This is what is set in DU as well with your default OP zip working fine.

Aside from that, bit more run time with hypervtnt gov. I like it a lot on stock frequencies, snappier than pegasusq with about same battery. It was fine up until 1500 MHz but likes to feeze at 1600. Sweet spot for me so far on it looks to be 300/1400. On pegasusq I can run 1600 MHz all day and night!

Fantastic work man... This kernel is amazing so far.
[Samsung Epic 4G Touch] jwhyte:
I just flashed crossbreeder on PAC with the hacked lz and with install cross breeder clears dalvik. I had no issues rebooting so is it possible that boot loops have to do with the cache partition?
[Samsung Epic 4G Touch] svicenty:
So crossbreeder works with lz
[Samsung Epic 4G Touch] jwhyte:
So far so good. [MENTION=4145127]thomas.raines[/MENTION] can confirm... Since cross breeder doesn't mess with the init.d shouldn't be any conflict. Running fine for me.
[Samsung Epic 4G Touch] thomas.raines:
Probably because I forgot to raise the max freq in hypervtnt...lol

Thanks for the reminder...I'll try to update tomorrow
[Samsung Epic 4G Touch] kvevand63:
Question.. does p4 contain frandom support? I have been running Agats 1.42f on TW, and CrossBreeder runs so much better with frandom supported kernel. Just asking as I see you had cherry-picked from Agats. About to update SlimBean I have on nandroid with p4.
[Samsung Epic 4G Touch] thedarksavant:
Hmm, I looked at the Crossbreeder updater script to see how it clears dalvik-cache so I could add it to my hacked zip. I prints it's clearing dalvik but I do not see any code that actually clears it :(

I have tried just clearing dalvik from advanced options and that resulted in a bootloop.
[Samsung Epic 4G Touch] jwhyte:
I get the usual android is upgrading after flashing crossbreeder. So the system thinks it cleared dalvik. Not sure what to look for so just thought to share.
[Samsung Epic 4G Touch] thedarksavant:
I'll be the first to admit I'm no expert with update scripts, so anything could be going on. I just don't see it.
[Samsung Epic 4G Touch] zimlokks:
it's something with building it in /cache/dalvik-cache/*

maybe updating the kernel version? stock WFTN is 3.0.61(i think)

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] CollinsB:
Which is dl link?

Im confused, is "smdk4412_p4.zip" the link for the Epic 4g touch LZ Phase 4 kernel?
[Samsung Epic 4G Touch] jordan0314:
Yes

Sent from my Galaxy [S2]
[Samsung Epic 4G Touch] CollinsB:
thanks!
[Samsung Epic 4G Touch] kchannel9:
Running well for me on Rootbox 4.1 20130627 build. Oc'ing has made this phone so fast.
[Samsung Epic 4G Touch] zombiegirl2010:
When I use this kernel (in Revolt or Dirty Unicorn) it drains my battery insanely fast! Before I knew it I was at 17%!! I flashed back to PACman (that doesn't use LZ) and I'm back to normal now. I don't understand what is going on. I cleaned flash both roms and had the same result each time with battery life.
[Samsung Epic 4G Touch] hazedabeast:
Is it over clocked?
[Samsung Epic 4G Touch] zombiegirl2010:
No
[Samsung Epic 4G Touch] jwhyte:
How long did you run the kernel? The first day is usually terrible with anything that has tweaks involved.
[Samsung Epic 4G Touch] zimlokks:
undervolting may help and also changing the governor

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] MajorTankz:
Please add a notice explaining that this will cause boot loops for many AOSP based rom users while you try to address that problem.
[Samsung Epic 4G Touch] ktempleton:
As far as i know it only causes that on a couple of ROM which if you had read that last few pages of the thread you that would have been explained along with a modified kernel that temporarily fixes that issue
[Samsung Epic 4G Touch] MajorTankz:
The chat in the last few pages appears vague and doesn't make much sense to anyone who isn't already aware of the problem. I read 2 -3 of the last pages before downloading and I assumed the chat was about a revision or update that wasn't released officially yet.
[Samsung Epic 4G Touch] hazedabeast:
Did u try overvolt and under clock?
[Samsung Epic 4G Touch] jwhyte:
Use the hacked kernel for PACman, CM and beanstalk. Others should be fine (slim, thinking bridge, revolt, du etc). Like always make a nandroid before flashing and if you experience extremely long boot ie boot loop restore nandroid and flash hacked kernel. The hacked kernel removes the cache wipes which caused the boot loop in cm etc. This goes without saying if you use hacked kernel do not wipe caches manually ever while running this kernel.

---------- Post added at 12:06 AM ---------- Previous post was at 12:03 AM ----------

See above.
[Samsung Epic 4G Touch] kchannel9:
I'm getting excellent battery life and it hasn't even been a full day of running it oc'd at 1.6ghz with +0.25 voltage increase at 1600.

Thank you so much Thomas

sent from my GS2/ET4G (AOKP/CM Rootbox 4.1, 20130627 build, with Lightning Zap kernel ver. 4) on Xparent Tapatalk2
[Samsung Epic 4G Touch] zombiegirl2010:
I have resolved the issue. I'm not sure why it was doing what it was yesterday, but I flashed Carbon and use it for a few hours and then tried a clean install of Revolt again. It's fine now. I know, it makes no sense...but it works now! :D
[Samsung Epic 4G Touch] kchannel9:
So.....fast......

sent from my GS2/ET4G (AOKP/CM Rootbox 4.1, 20130627 build, with Lightning Zap kernel ver. 4) on Xparent Tapatalk2
[Samsung Epic 4G Touch] dtr145r:
Was this fixed so we can wipe cache?