yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] kvevand63:
I couldnt tell you. I am on an unactivated device and wifi only, which I have no issues with. I uninstall all phone, sms etc apks. Great ROM though.
[Samsung Epic 4G Touch] Zxo0oxz:
Technically there isn't a difference since 4.3.1 was just a minor fix for the Nexus 7. As far as a release, I've been lazy on making one.
[Samsung Epic 4G Touch] hakcenter:
Hey..

Crazy idea, back port your kernel to 4.0.4.. I would suggest using my github but i want to remove kexec from it because I'm pretty certain that's causing permission and mounting differences from what the inits say to do and what actually happens.

Maybe I'll tag a new version then you can work on a back port?
[Samsung Epic 4G Touch] Zxo0oxz:
Tag me a good 4.0 source and I'll do it.
[Samsung Epic 4G Touch] :
Hmm.. I flashed the 6.3 test kernel and phone kept FC'ing. On CM10.2
[Samsung Epic 4G Touch] zimlokks:
It's been happening to me as well with any kernel other than stock, I just decided to delete the phone apk, might try to get a logcat but that makes it impossible while using emulator terminal
[Samsung Epic 4G Touch] Zxo0oxz:
Probably some inconsistency with the ramdisk and recent builds. I'll push out a build later that should fix it.
[Samsung Epic 4G Touch] zimlokks:
We appreciate it man :D
[Samsung Epic 4G Touch] exProphecy:
I'm having a serious amount of lockups (at 300/1100 alicornq/bfq but tried other settings still same..) using SlimBean Build 7 4.2.2 :(

Is there anyway to revert back to the original kernel for it??

EDIT: WAIT I just realized I think SlimBean build 7 came with LZ kernel already in it.. could that be the issue? since I flashed over it with this?
[Samsung Epic 4G Touch] exProphecy:
I see.. any idea how do I would go about fixing this? Would flashing over the ROM and just wiping cache/dalvik work?
[Samsung Epic 4G Touch] kvevand63:
Look in your init.d folder. I believe LZ Kernel includes init.d scripts that will conflict with Blasphemy. Delete these scripts, reboot to recovery, wipe cache and dalvik. I would also recommend a fresh download of Blasphemy (make sure m5d matches also) and reflash kernel after the aforementioned process.
[Samsung Epic 4G Touch] exProphecy:
Can I just delete everything in there?
[Samsung Epic 4G Touch] kvevand63:
I would not delete 50selinuxrelable. Any thing else you can. The main concern is to eliminate any scripts that will conflict with Blasphemy, which does not include any scripts. Personally, I would do a clean re-flash of the ROM, delete the conflicting init.d scripts, flash Blasphemy.
[Samsung Epic 4G Touch] exProphecy:
Okie seems like that fixed it! I'll have to use it for a whole day to see if I get more lockups tho. Thank you!
[Samsung Epic 4G Touch] btvolta:
I just flashed Baked Bean 4.2.2 last night to try it out. I then flashed the Blasphemy kernel 6.2 that is for 4.2 Roms. Just a few minutes ago, I lost data and had to reboot to get it back. I thought this issue was only happening on 4.3 with kernels that are developed for 4.3 Roms. Does anyone know which is the most stable of the 4.2 blasphemy kernels to use so I don't lose data, or should I just reflash and use stock kernel that came with the rom because I didn't lose data until I changed the kernel?
[Samsung Epic 4G Touch] jwhyte:
Depending on when black bean was made it may be the old kernel source and not compatible with blasphemy.
[Samsung Epic 4G Touch] btvolta:
The most current build was 5/16/2013. The data worked overnight, but went out this morning. I dirty flashed the rom to get back the original kernel. The first of the year, I am most likely getting a note 3, so I am just going back and playing with roms I've never used before. There aren't many that I haven't been on, but there are a few.
[Samsung Epic 4G Touch] eigokyoukan:
Note 3 is supurb... Got a buddy with one and its just so damn nice. Plus the drop tests I saw were DAMN impressive. I've never seen a smartphone take a 4ft fall face first on concrete with no protection and survive... Til the note 3 :D
[Samsung Epic 4G Touch] btoddweber:
So is this OK to use on Revolt 4.2.2??
[Samsung Epic 4G Touch] mudkipz:
Yes
[Samsung Epic 4G Touch] glenesis:
Does this kernel include

/proc/mic_level? Alledgedly, if we have a kernel with that included, we can use an app from the Play Store as a GUI to control input gain on the mic, and maybe take video footage without so much audio distortion. The app is called HD2 Mic Control. The app looks cool, but I have not found a kernel that supports it yet, and I would love to be able to record video of musicians without blowing out the sound :(

Afro Brick Is In Your Face Rock!!
[Samsung Epic 4G Touch] TULOA:
Thanks for bringing the kernel up to 4.3.

Yesterday left to work with a full charge. Died two hours later. Charged for 15 minutes off and went to 40%. Died after another two hours. Repeated through the night.

Installed the kernel and set the SIO and Pegasusq governer and now left with 100% and is still at 50%+ 7 hours later.

Owe ya one man lol.
[Samsung Epic 4G Touch] Zxo0oxz:
I don't believe so, give it a try. I was able to find this patch to enable it, but it's for different hardware. I'll see what I can do. Also currently out of a build server. http://dl.xda-developers.com/attach...11f65b/52890b4c/7/0/3/6/2/3/diff_mic_gain.txt
[Samsung Epic 4G Touch] Zxo0oxz:
Hey guys, I've finally switched over to 4.3. I'll pump out fresh new 4.3 and 4.4 builds before the weekend ends.
[Samsung Epic 4G Touch] LucentBirch:
Freezing continuing...

I've gone back to 4.3 DU and flashed latest Blasphemy...I have been running it without Comadose because I was certain it coupled with Blasphemy was causing my phone to freeze on the black screen, but it turns out that was wrong. I am still experiencing the black screen lockups on Blasphemy and I haven't been able to find out why. To my knowledge no one else seems to be experiencing it at all...so why me? Is there anything I can do do diagnose it?
[Samsung Epic 4G Touch] jwhyte:
I've had same issue with blasphemy on 4.2 with cdose. It works either freeze or act like it didn't want to wake up. Just got used to a battery pull once a day it was never more than that.
[Samsung Epic 4G Touch] thedarksavant:
You are not the only one. I went to DU 4.2 to get away from the sleep of death.

I've seen posts from folks claiming if you use the next to latest Blasphemy the SODs go away.
[Samsung Epic 4G Touch] Zxo0oxz:
Sorry for the delays... working on some new stuff

Edit 6.6 for 4.3 posted.

Nothing really changed aside from the stuff that was in the previously testing builds and syncing with upstream, testing some new stuff as well that may make it in.
[Samsung Epic 4G Touch] LucentBirch:
This new one turned my hardware key lights back on even though they're turned off in the device settings...
[Samsung Epic 4G Touch] jc.m:
I did flashed it too and lights are working good
[Samsung Epic 4G Touch] gamepro602:
4.2 or 4.3?
[Samsung Epic 4G Touch] LucentBirch:
4.3
[Samsung Epic 4G Touch] Krowbarr:
Same deal here. Reverted back to 6.2 4.3 kernel.

Sent From My Nexus 7 2013/Pacman Rom/faux mainline kernel 007 r2!
[Samsung Epic 4G Touch] LucentBirch:
I don't want to use 4.2.2 though! I experience the 'sleep of death' even more on 4.2.2 on Blasphemy... also, Standby on 4.3 has been phenomenal for me despite the freezing...
[Samsung Epic 4G Touch] thedarksavant:
You can use the 4.3 DU, just try the 6.1 Blasphemy. I see there's a 6.6 now, which you could also try.
[Samsung Epic 4G Touch] LucentBirch:
The point is no matter which version of Android I'm on I experience a lockup with blasphemy...never did with LZ
[Samsung Epic 4G Touch] Zxo0oxz:
As far as the lights, they've never really bothered me, but it seems to be an issue now, so I'll start looking into that. Also, which ROM are you guys on when experiencing this?
[Samsung Epic 4G Touch] ps3hacker3:
I'm on the latest hood Pope 4.3 and haven't found an issue yet running your latest 6.6
[Samsung Epic 4G Touch] Zxo0oxz:
That's what I expected.
[Samsung Epic 4G Touch] Krowbarr:
I'm running Dirty Unicorns 4.3.1

☞Owner/Operator Samsung E4GT running Dirty Unicorns 4.3.1 Powered by Blasphemy!

We were born in a time where if something was broken we would fix it and not just throw it away
[Samsung Epic 4G Touch] ps3hacker3:
Could be something I did but I just had one sleep of death I guess you could say while playing music and continued to play the album completely through before I had to battery pull never seen this before lol
[Samsung Epic 4G Touch] Inane_Asylum:
Is there a 4.3 ROM this kernel works with that doesn't get the SOD or rotation reboot bug? I tried 6.1 and 6.2 on DU and ReVolt and had to flash back to 4.2 because the lockups/reboots were just too often and inconvenient for a DD.
[Samsung Epic 4G Touch] mw86:
Looking forward to your 4.4 kernel. I was on 4.3.1 but trying the new CM11. Blasphemy ran great on 4.3.1
[Samsung Epic 4G Touch] LucentBirch:
Could it be something with aokp then? Cause both revolt and DU are built on it...I went to hood pope gonna try 6.6 tomorrow
[Samsung Epic 4G Touch] mholloway:
Last night installed hood pope and 6.6 kernel and all was fine this morning getting sod.:( back to 4.2.2 for me
[Samsung Epic 4G Touch] Inane_Asylum:
By the way, getting SOD with the 6.2 kernel for 4.2. Flashing 6.1 with my fingers crossed.
[Samsung Epic 4G Touch] Zxo0oxz:
Haven't looked into it just yet, but 4.3 has undergone a lot of changes for our device. This version is built with cm10.2's initrd, so something has probably moved around.
[Samsung Epic 4G Touch] asd87:
I don't think it's the kernel. I get lock ups and SOD when running any AOSP ROM. I think the kernel is just fine and it's the ROMs themselves.

I went back to TouchWiz ROMs because they have almost no issues. Can't wait to order a nexus 5 though!
[Samsung Epic 4G Touch] Zxo0oxz:
I was referring to the lights issue. I think I'm gonna come up with a boring kernel with changes less likely to cause lockups and whatnot. As far as AOSP stability, haven't had any issues on stock CM10.2.
[Samsung Epic 4G Touch] Inane_Asylum:
Flashing 6.1 cleared up the SOD for me on Dirty Unicorns. I wish they were predictable enough I could get a logcat of one, but as it is, I'd have to keep it recording for hours hoping for a lockup :-/

How stable is 6.6? I've been wanting to go back to 4.3...
[Samsung Epic 4G Touch] NavalFluff:
I had a lot of issues with 6.2 while running cm10.1. Random freezes, lag, SOD. Haven't had any since flashing 6.1. In my humble and not really all that educated opinion I think it may be a problem with the kernel, as I've never had SOD and such running stock AOSP roms or any build before 6.2.
[Samsung Epic 4G Touch] Gazzuk:
No problems for me. Great work!

Samsung E4GT 4.2.2 CM10.1 - Blasphemy 6.2 Kernel - Operation Killjoy 10.2.13 rc7 Tweaks - Xposed Theme
[Samsung Epic 4G Touch] thedarksavant:
I'm running "The Gentlemen" which is CM 10.1 from hackcenter. I'm running the kernel that came with it, which is Blasphemy but I do not know which version. Considering the age of the build, I'm guessing way before 6.1.

I had lockup issues overclocking to 1600. I remember early versions of Blasphemy having bad voltage settings at 1600. I've since changed to 100-1000 and have not had a single issue, other than a minor annoyance that I can never seem to achieve a flat battery curve even in deep sleep.
[Samsung Epic 4G Touch] NavalFluff:
What governor are you using? I've stuck with pegasusq for a long time now and not to brag but just yesterday I was averaging 5 hours per 10% of battery. That being said, I don't use my phone all that much and I have deep sleep battery saver set to aggressive and the app Greenify. Try Greenify if you haven't, it works wonders on your battery life :)
[Samsung Epic 4G Touch] Gazzuk:
I'm on the latest official nightly

Samsung E4GT 4.2.2 CM10.1 - Blasphemy 6.2 Kernel - Operation Killjoy 10.2.13 rc7 Tweaks - Xposed Theme
[Samsung Epic 4G Touch] Unjustified Dev:
I will upload a 4.4 compatible version in a few hours.
[Samsung Epic 4G Touch] mw86:
Cool Ill be glad to test when you post it :)
[Samsung Epic 4G Touch] Unjustified Dev:
I will post it with my cm-11.0 build
[Samsung Epic 4G Touch] ps3hacker3:
I'll be more than happy to test it for you as long as I am home the moment it gets uploaded by you... Good job my man nice to meet you here I'm sure many of us would greatly love to see another build as well
[Samsung Epic 4G Touch] Unjustified Dev:
I plan on doing some great things with this device. Thanks to someone from xda who donated it. I really need a server to compile on. My PC takes hours to build , but it's coming .
[Samsung Epic 4G Touch] ps3hacker3:
How good of a system does it really take to actually compile roms at a decent speed like this man? What good CPU? maybe how much ram? What does it take?
[Samsung Epic 4G Touch] Unjustified Dev:
A good decent build time requires a lot. The server I previously used was an eight core i7 and took like 40 minutes. It probably had 8gb of ram. A quad core isn't that bad depending on the amount of ram.
[Samsung Epic 4G Touch] thedarksavant:
I use alqornq which I've heard use turned better for our dual core processor.
[Samsung Epic 4G Touch] ps3hacker3:
Hmm interesting man right it's not server or anything.... But I have a slight gaming rig with 8 core 4.0ghz and 8 gig ram
[Samsung Epic 4G Touch] mw86:
Intel is the way to go. They have some real tanks for cpus.
[Samsung Epic 4G Touch] mw86:
I saw you are working on a build and borrowed some commits from the other CM11 build posted. Can't wait to try your rom and kernel combo.
[Samsung Epic 4G Touch] Robles23:
Hello! I need some orientation regarding this Kernel.

Yesterday I flashed the latest version of this Kernel and I've been having horrible experiences with it. It lags at first, and immediately after that it freezes. I have to remove the battery and restart my device. I continue using my device and the same thing happens again. Is anybody else experiencing issues with the latest version?
[Samsung Epic 4G Touch] thedarksavant:
I have had Sleep Of Death (SOD) but I have not experienced lagging and constant freezing.

Did you match the kernel to the Android version? AKAIK, 6.6 only runs on 4.3. If you are on 4.2, I suggest 6.1 over 6.2.
[Samsung Epic 4G Touch] Robles23:
Hello! Thank you for your response! I'm currently running CM 10.1 android version 4.2.2. I will give 6.1 version a try and hopefully runs well. Also, you must boot your phone into recovery and flash this kernel correct? You don't use mobile odin to flash this correct? Relatively new to this. Sorry =/
[Samsung Epic 4G Touch] thedarksavant:
Yes, I just flash from recovery.
[Samsung Epic 4G Touch] Robles23:
Thank you sir! I tried v6, v6.2 and v5 but not v6.1. I will give 6.1 a try and post results later. Ones again, I appreciate your help.
[Samsung Epic 4G Touch] Zxo0oxz:
I build on a server with 2 quad core i7 based xeons (16 threads total) and 32GB of ram. Generally pumps out a build in less than 30 minutes.
[Samsung Epic 4G Touch] Unjustified Dev:
Want to share? :p
[Samsung Epic 4G Touch] Zxo0oxz:
Can't. It's located in a personal friend's closet. If I actually had some rackspace, I'd totally consider it.
[Samsung Epic 4G Touch] Krowbarr:
Running Kitkat on my S2 and looking forward to a Blasphemy 4.4 kernel:D

☞Owner/Operator Samsung E4GT/Villuminati Rom 4.4.1 Kitkat

We were born in a time where if something was broken we would fix it and not just throw it away
[Samsung Epic 4G Touch] minikirchner:
+1
[Samsung Epic 4G Touch] easyrider77:
Just out of curiosity.....I've run into some volume issues with some roms, where the volume is really really low.

Since I am fairly new to understanding things I was talking to a dev and he said that the volume and 3g and wifi not connecting can be contributed to the kernel, and I've also seen kernels that have a volume hack of sorts in them......this being the case, does this kernel include a volume increase fix perhaps?

I'm planning on running carbon rom with this kernel, so I hope the volume isn't low like most the other roms I've tried.
[Samsung Epic 4G Touch] Linux guy:
Well I'm not 100% on why volume is bad in custom ROMs for this phone but I know it's something that was fixed in KitKat. So anything from aosp before kit Kat will give you that volume bug.

sent from tumblr
[Samsung Epic 4G Touch] easyrider77:
Well it depends really, I have used the latest nightly CM 10.1 build android 4.3.1 (still JB and not KK), and volume works fine on it, yet on other roms, the volume is low. Basically some work and some do not but it seems to relate the the kernel being the issue.

That's why I was curious about the kernel being the issue, because that would make perfect sense being as they all use customized kernels normally, and that can cause issues with stuff like no wifi, no 3g data, low volume.

They have a volume hacked kernel out for like the s3 and some other phones, but you can't hardly use that kernel on this phone :).
[Samsung Epic 4G Touch] Linux guy:
If it is a kernel thing then this kernel has it too. But that's a silly thing to worry about. You should get DSP, or I think there's a work song around.

sent from tumblr
[Samsung Epic 4G Touch] easyrider77:
Well as far as I have tested there is no fix. I've tried dsp, and multiple multiple other voule apps and hacks for this phone, nothing works.

Most if not the majority of them only adjust the the bass as apposed to the volume level.

I found one workaround that worked, and adjust the volume up for the headphones, but only wors for the headphones, and while this is nice, it's not a fix for the entire system. The ringtones and notifications come from the speaker phone, not the headphones, therfor you still ahve a low volume issue, where you can't hear your phone ring or can't hear a message come in.

It's a well known issue, and as of yet, after multiple days of google searching, there still is no fix, so people revert back to Touchwiz on this phone because it doesn't have the issue.

I've exhausted flashing many many numerous roms and tweaks and fixes, in hopes for a fix and to my sad findings, they just do not work.

There is also a known gps lock-on issue with these phones as well.

I have found one that finally works well and that's the latest CM 10.1 build, so that's a very good thing, but the rest have either low volume or a wonky GPS lock-on issue, where gps takes forever to lock on IF it locks at all. This kernel had a GPS lock-on issue as well as a no wifi issue at first, but got fixed, so it can very well be pertaining to the kernels being the main culprit.
[Samsung Epic 4G Touch] Linux guy:
Well personally I don't use this kernel, I just like helping. I'm currently on a test build for slim kat and the volume is not an issue. Just data. But if you want a ROM without the volume bug get dastins villuminati. It ran great the few days I had it and it has GPS and data too. Did I mention its kit Kat?

sent from tumblr
[Samsung Epic 4G Touch] Linux guy:
Oh yeah I remember reading your reply. If it doesn't work I'd recommend going back to the cm nightlies. I think they're stable enough to use daily. I don't do it myself because I just love cutting edge. In glad my phone isn't activated because I never worry about data ^^. And I can do my part by testing before people who can't have it crashing mid day. Good luck!

sent from tumblr
[Samsung Epic 4G Touch] easyrider77:
Well let me know what I can do or test out as far as this goes.....I have flashed so many roms and fixes it's made my head all woozy lol, I've been flashing like a madman for almost 2 weeks now trying fixes, and roms and etc....so let me know, it won't bother me a bit.

Don't think I've had a phone fully up and running IE: all my apps and stuff for the last 2 weeks, everything I install is for basically testing stuff out.

I'm on the Dec 14th release of cm10.1 and was wondering if this kernel would work on that, or should I refrain from using it......just outta curiosity will it like mess settings or something up.
[Samsung Epic 4G Touch] ps3hacker3:
Just saying man but if data is the only issue on that slimkat build of yours.... I would kill to test it out myself (^_-)
[Samsung Epic 4G Touch] Linux guy:
Well on that case. Any one interested go to the slim bean thread by ktemplon and start reading more or less at page 187.

sent from tumblr
[Samsung Epic 4G Touch] ps3hacker3:
All my reading up to the latest which I think was today maybe I'm wrong but none of them could be successfully booted and the ones that did didn't get past the activation screen?
[Samsung Epic 4G Touch] Linux guy:
Well almost. I managed to do a little work around. It has no data but if you want message me and I'll take you step by step.

sent from tumblr
[Samsung Epic 4G Touch] Robles23:
Need additional help.

Hello guys! Good afternoon. I've previously asked for help regarding this Kernel on this Thread but I continue to have issues with it

Here is my current setup:

>Epic 4G Touch (Sprint)

> CyanogenMod 10.1 Nightly D710 2013-11-03

>Android version 4.2.2

So far, I've tried version 5, 6, 6.1 and 6.2 of this kernel. All of them not working for me. The only thing i am experiencing are random freezes at times where the phone completely freezes. The only solution to that is me removing the battery and power on the device again. I've noticed this happening much more often when Im using the web browser. And few days ago, this random freeze happened again while playing a game. (Heavy CPU usage) However, this issue does not happen when the CPU is under a small load. One more thing that I want to point out and that I think its causing this issue is my 10.1 Nightly. The 2013 - 11 - 03 Nightly Version of 10.1 was the last official Nightly build.

If anybody here that is using this Kernel and running Official Nightly Builds for 10.1, could please tell me what Nightly version you are using I will gladly appreciate it.

Basically, I am looking for a stable combination of this kernel and a 10.1 Nightly Build.

Thanks Guys! :good:
[Samsung Epic 4G Touch] gamepro602:
I'm using a Christmas nightly and that one was solid for me...

Its CM 10.2 btw
[Samsung Epic 4G Touch] Robles23:
I dont want to jump into 10.2 because I want 4G. Thats the only thing holding me back. If not I would have flashed a 4.4 ROM.
[Samsung Epic 4G Touch] thedarksavant:
You could try The Gentleman which is 10.1.3 and I believe has Blasphemy backed in -> http://xdaforums.com/showthread.php?t=2412208
[Samsung Epic 4G Touch] Robles23:
Thank you very much. I will look into this and decide if it works for me. Thank you for your help. Much appreciated.
[Samsung Epic 4G Touch] exProphecy:
Has anyone used this kernel with success and no issues on 4.2.2 SlimBean Build 7? If yes, are there any special steps because i keep getting freezes/lockups and SODS when I install it
[Samsung Epic 4G Touch] Linux guy:
Make sure your using the right version. You might need to wipe cache. It worked for me but I don't remember which version it was. Just make sure it's for 4.2 and maybe try different ones

sent from tumblr
[Samsung Epic 4G Touch] NavalFluff:
I just installed the lastest CM 10.2 nightly, and tried to install this kernel after setting everything up only to have the phone service stop working. I tried 6.6, 6.2, and even version 4 of the 4.3 build of Blasphemy. Only using Comadose 3.5 tweak, any suggestions?
[Samsung Epic 4G Touch] thedarksavant:
You are aware you have to use an ICS modem with cm on this phone, no?
[Samsung Epic 4G Touch] HighxVoltage:
I don't think it had anything to do with the modem. Even with an ICS modem the phone app FC's.
[Samsung Epic 4G Touch] NavalFluff:
As far as I know fl24 is an ics modem, and it's the one I'm on right now.
[Samsung Epic 4G Touch] blackmeth:
I'm using FL26 don't think it would make a difference though
[Samsung Epic 4G Touch] bigmike6200:
I really wish this Kernel was setup for 4.4. It would be nice in CM11.
[Samsung Epic 4G Touch] Linux guy:
Vanir uses this.
[Samsung Epic 4G Touch] bigmike6200:
Yes it does. :good: Where's the update for 4.4.4? I am on 4.4.2
[Samsung Epic 4G Touch] flamadiddle:
Are there any live mirrors for this kernel? I'm trying to revive an old E4GT, and was directed here.

But http://f.the-beach.co/ is unresponsive to me.