yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] lvpre:
Not sure if you have given up or found it, but I was able to flash CM11 with this recovery attached. Just flash in your current recovery; reboot recovery; wipe; install new ROM. Probably only works with CM/AOSP roms though.

This will install Philz recovery. Basically a modded CWM recovery.
[Samsung Epic 4G Touch] kanaan360:
trying to revive my step moms old e4gt making sure at least two people have had luck following this guide but replacing the blasphemy kernel flash with flashing philz touch

the phone has been soft bricked for the last 6 months i just dont wanna hard brick it
[Samsung Epic 4G Touch] Zxo0oxz:
This kernel doesn't include a custom boot screen. I just think it's a pointless vanity change. Since LZ included one, and this one doesn't it will still have the LZ boot screen. Similarly, if you install this on top of LZ, you'll still retain all the LZ scripts/tweaks that are started on boot.
[Samsung Epic 4G Touch] LucentBirch:
Do you recommend then I do a clean flash of ReVolt and then flash this kernel again?
[Samsung Epic 4G Touch] Zxo0oxz:
Personally, that's what I would do. However, nothing is stopping you from using this kernel in conjunction with the LZ tweaks/scripts.
[Samsung Epic 4G Touch] LucentBirch:
See, I wish I knew more, but I have no idea what the tweaks and scripts do...
[Samsung Epic 4G Touch] Master_Ellis:
Hi OP

Are both kernels for Android 4.2.x or is the second version for 4.3 only? Confused
[Samsung Epic 4G Touch] jwhyte:
Both are 4.2
[Samsung Epic 4G Touch] Zxo0oxz:
Correct, I'll have 4.3 up in a few hours. Busy day at work :silly:
[Samsung Epic 4G Touch] Zxo0oxz:
4.3 build posted, it is UNTESTED, please let me know if it works.
[Samsung Epic 4G Touch] digitalmorphinex:
Anyone else having problems with USB transfer with this kernel? I know its suppose to charge like its plugged into the wall but I didn't see it'd say USB transfer wouldn't work.. :S great work though!
[Samsung Epic 4G Touch] DEF3NDER:
Is it just slow or does it not work at all? USB transfer is always super slow on aosp.
[Samsung Epic 4G Touch] Zxo0oxz:
daniel@rarity /r/m/d/40AA-07D1> dd if=/dev/zero of=testfile bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 181.298 s, 5.9 MB/s

No problems here....

Edit: Which rom? 4.2 or 4.3?
[Samsung Epic 4G Touch] digitalmorphinex:
4.2.2.. Hmmm..
[Samsung Epic 4G Touch] Soured Lie:
Nice. Running now. I am having zero issues right now. GPS gave me a lock first go. No reboots or anything that others have reported. I left the old lz scripts in there. Running on latest DU. :good:

EDIT: Awesome. This is charging dumb fast off of USB. Perfect.
[Samsung Epic 4G Touch] Zxo0oxz:
Glad to hear you're liking it. I think I've encountered one issue so far, and that seems to be occasional ghost touches. But I think it's more likely to be hardware or a dirty screen. If anyone sees this issue, let me know.
[Samsung Epic 4G Touch] :
Haven't experienced any ghost touches since running v2
[Samsung Epic 4G Touch] thatdudepoops:
I got it to run on hood pope.

Everything is running fast and snappy.

UV/OC all good 25-1600

Not so lucky with GPS, it locks but accuracy is at 3000 meters.
[Samsung Epic 4G Touch] thatdudepoops:
Whoops ^^
[Samsung Epic 4G Touch] digitalmorphinex:
After reflashing I can now use the USB.. Might have been my PC but works now. Nice job!
[Samsung Epic 4G Touch] abadasstanker69:
Check your pm's bro. Should help progress :)
[Samsung Epic 4G Touch] LucentBirch:
I have had my screen not wake up several times now and had to reboot every time. Anyone else with the same issue?
[Samsung Epic 4G Touch] Krowbarr:
Same here with SOD.

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v2 kernel.

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] Dudebowski:
Seems to be working well for me so far. Overclock to 1.4, under clocked to 25. Pegasusq and sio. Under volt -50. Slapped killjoy tweaks on it too.

Thanks for picking up the progress for our d710 kernel.

Any chance for adding tun.ko?

sent from the mobo
[Samsung Epic 4G Touch] Zxo0oxz:
Hi there, sorry to hear that. Anyways I did experience this, but it was on a very early unreleased version, and an unofficial rom. I've been watching my phone very carefully for stability issues, and it seems to be doing great on cm10.1 official nightlies, no instability whatsoever. What ROM are you on?
[Samsung Epic 4G Touch] OldMansGhost:
I'm on 10.1 also and having no problems. Good job on this, Zxo0oxz. :thumbup:
[Samsung Epic 4G Touch] jwhyte:
I'm running it on the latest beanstalk with comadose. Had a couple reboots initially but running great now! Smartassv2 vr 900/50.
[Samsung Epic 4G Touch] LucentBirch:
ReVolt
[Samsung Epic 4G Touch] Krowbarr:
I'm running Pacman. 200/1.5 ondemand/sio. No tweaks or uv.

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v2 kernel.

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] Zxo0oxz:
No need to include tun.ko, it's already built in.
[Samsung Epic 4G Touch] Dudebowski:
I guess this app I'm using doesn't even check then and just sideload it's own. Sits in my sdcard root... I assume it's from the vpnclient anyway.

Thanks for being awesome. Cheers

sent from the mobo
[Samsung Epic 4G Touch] Zxo0oxz:
New build posted in the usual place. Changes include:

added a tweaked version of pegasusq I've dubbed alicornq

added smartassv2 governor

BFQ I/O Scheduler

lowmemory killer update backported from 3.4

Deadline tweaks

fuse tweaks

mutex tweaks

dynamic fsync fixes-- basically safeguards in the event of a reboot

a few other generic ARM fixes, most of which backported from Linux 3.4
[Samsung Epic 4G Touch] comptonhubbard:
great DLing it now.
[Samsung Epic 4G Touch] ps3hacker3:
No 4.3 build on the update?
[Samsung Epic 4G Touch] deaver_92:
Tried downloading 4 times. Zip was corrupted each time.

Edit: Tried downloading on my computer as well. Still corrupted.

Sent from my totally awesome E4GT rockin CM10.1 OFFICIAL w/ LZ Kernel overclocked to 200/1600 w/ Ondemand/Sio
[Samsung Epic 4G Touch] glenesis:
4.2v3 seems to be playing nicely with SlimBean build 7. GPS locks fast, WiFi works, 3g works, all my apps seem fine. Thanks, Zxo0oxz!

Edit: Right after I posted this, I OC'd (I did not check "set at boot")(cfq, smartassv2, 25/1400). A few minutes later, the phone froze solid running Chrome browser. Rebooted, and it froze again a few seconds after my launcher loaded. Reflashed v2, and got a few freezes, too, so I nandroided back to Slim 7 with LZ.

I will try to recreate the errors and grab you logs, as soon as time permits.
[Samsung Epic 4G Touch] Zxo0oxz:
I'm going to disable cloudflare on the server and set up a mirror. I apologize.

As far as the instabilities, I'm pretty new to this, but any logs you can pull up, I'd be happy to look into it.

Edit: I'll have a 4.3 build out soon as well. I was working on it last night, but got tired and went to bed.

Edit2: here's a mirror of v3 for anyone having trouble downloading it from my server.

http://d-h.st/QMt
[Samsung Epic 4G Touch] deaver_92:
That one worked thanks!

Sent from my totally awesome E4GT rockin CM10.1 OFFICIAL w/ LZ Kernel overclocked to 200/1600 w/ Ondemand/Sio
[Samsung Epic 4G Touch] gamepro602:
What does alicornq gov work? I notices that it scaling is lower:confused:
[Samsung Epic 4G Touch] deaver_92:
Installed v3 last night before I went to sleep. Woke up this morning and the phone was frozen. According to the clock it froze about 15 minutes after boot. Back to v2 for now. The following is what I was running when it froze.

Cm10.1 8/23 nightly

Blasphemy v3

Alicornq/noop

1600/200 mhz

Sent from my totally awesome E4GT rockin CM10.1 OFFICIAL w/ LZ Kernel overclocked to 200/1600 w/ Ondemand/Sio
[Samsung Epic 4G Touch] digitalmorphinex:
Yeah I keep having freezing issues on version 3.. :(
[Samsung Epic 4G Touch] gamepro602:
No issues here, and I'm on the latest CM nightly :)

CM 10.1 8/27 nightly

Alicornq/deadline

900/25 MHz

---------- Post added at 12:27 PM ---------- Previous post was at 12:20 PM ----------

And also post a logcat if you have freezing issues, saying "it keeps freezing" won't help :rolleyes:
[Samsung Epic 4G Touch] Zxo0oxz:
Yeah, it was working fine for me, then I get to work today and my phone keeps freezing. :( And that was after a whole weekend of testing. I'm going to try to debug it later. Unfortunately, I'm about 1 hour into a 15 hour shift so I won't be able to touch it for a day or 2.

Edit: in the meantime, I'll gladly take pull requests if anyone else is up to it ;)
[Samsung Epic 4G Touch] Zxo0oxz:
Due to the instabilities in v3, the next version will be rebased on the cyanogenmod kernel, only retaining the key features. From there I will slowly add back the tweaks known to be stable after a good amount of testing. For now I recommend going back to v2.
[Samsung Epic 4G Touch] :
There was instabilities in v3? O.o
[Samsung Epic 4G Touch] noc_t:
I've been using v3 with out a hitch since it was released
[Samsung Epic 4G Touch] digitalmorphinex:
I noticed the battery seems to get incredibly hot right before it freezes.. I'm gonna read up about how to do log cats and post one since I'm nab..
[Samsung Epic 4G Touch] gamepro602:
Yea, i didn't notice any I stabilities at all:what:
[Samsung Epic 4G Touch] jwhyte:
Running great for me. One freeze in last 36 hours
[Samsung Epic 4G Touch] Krowbarr:
+1 same here.

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v3 kernel.

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] :
Haven't encountered any freezes since I last flashed it (2 days ago?)

No freezes. On official CM10.1. Now trying it out on RootBox, so far no locks ups or freeezes.
[Samsung Epic 4G Touch] deaver_92:
Try multitasking (play music while doing other stuff). I had v2 lock up on my twice in 20 minutes doing that. I had forgotten to change the performance stuff so I was running 1200/200, Ondemand, and CFQ at the time.

Sent from my totally awesome E4GT rockin CM10.1 OFFICIAL w/ LZ Kernel overclocked to 200/1600 w/ Ondemand/Sio
[Samsung Epic 4G Touch] Zxo0oxz:
For me, I can do a million things at once (reddit, music, irc, web browsing) and it won't crash, but yesterday when I got to my office and started texting a friend, it crashed 5 times in a row.

Edit: I also run my phone at 900mhz so I doubt it's OC related
[Samsung Epic 4G Touch] :
Only times it froze is when I flashed it over CarbonROM and hakcenter's CM10.1 builds.

Hasn't froze on me on Rootbox. Phone as been on for 10 hours.

Current setup is 1400/200 row/alicornq
[Samsung Epic 4G Touch] cephaus:
Yeah, carbon and this kernel dont play well together,
[Samsung Epic 4G Touch] mlock420:
I would like to know how would I know if it's working correctly where do I look
[Samsung Epic 4G Touch] Zxo0oxz:
Uh? How do you know it's installed? Check system information, kernel version should be something like 3.0.93-blasphemy-3...
[Samsung Epic 4G Touch] kvevand63:
Running v3 on E4GT/Beanstalk 1.330, 100/1400hz, sio/pegasusq for the last 48 hrs. No freezes, SODs, running smooth! Really appreciate your contribution, nice to have another kernel option for CM 10.1 on our device. Thank you!
[Samsung Epic 4G Touch] Zxo0oxz:
Yeah, after it went totally unstable, my phones been running smoothly for the last 48 hours. I still want to track down the issues though.

Also, I haven't forgotten about you guys. I work 2 jobs and freelance websites in my spare time, so I work on phone stuff when I can.
[Samsung Epic 4G Touch] Soured Lie:
No issues to report with v3 on DU. Also I don't have the android is taking up significant amount of battery percentage as reported by others. Mine stays at 6 to 12 percent.

Pretty happy with the kernel so far after running for a couple of days.
[Samsung Epic 4G Touch] gamepro602:
Im using the 4.3 kernel and it makes it run smother than before, i don't even need to install tweaks :victory:
[Samsung Epic 4G Touch] kvevand63:
Update to my previous post: thank you for updating your OP with warning regarding unstability with v3. After running smooth for a couple of days on v3, I discovered an hour ago that my device at idle (off the charger) was running at 57 to 98% on the cpu (temp at 156°f), and would not cycle in to deep sleep. Reverted back to v2, running normally once again. E4GT/Beanstalk build 1.330. Btw.. no tweaks other than CrossBreeder.
[Samsung Epic 4G Touch] Krowbarr:
Problem here also. Reverted back to v2. Look at that Deleted Wakelock number.

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v2 kernel.

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] thatdudepoops:
I love this kernel. I never been able to UV as far as this
[Samsung Epic 4G Touch] hakcenter:
deleted_wakelock is your wifi if you eventually toggled it off.
[Samsung Epic 4G Touch] Zxo0oxz:
Not necessarily. deleted_wakelock can be any wakelock that's been deleted. But from a quick google search, it's generally related to wifi on android.
[Samsung Epic 4G Touch] Zxo0oxz:
Thanks, but there's no logical reason why this one should be able to UV any further than previous ones, as the other ones all use the same OC/UV commit :p

For anyone brave enough to test: http://f.the-beach.co/stuff/kernal/blasphemykernel-4-4.2.zip

This should be the most stable release so far. Let me know what you think.
[Samsung Epic 4G Touch] thatdudepoops:
This kernel is more stable at those freq. Other kernels always freeze up, hard and soft reboots, etc. I havnt had this good of battery life ever on this phone
[Samsung Epic 4G Touch] gamepro602:
Can you release a test zip for 4.3:p
[Samsung Epic 4G Touch] Krowbarr:
Just flashed and Wi-Fi is not working. Here's a log I just pulled with Wi-Fi turned on. Hope it helps. 3G is working. http://db.tt/OU2Y9Jr7

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v2 kernel.

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] jwhyte:
Running great for me. Blasphemy v3 Alicornq sio 900/50

With comadose v2.1
[Samsung Epic 4G Touch] digitalmorphinex:
WiFi doesn't work for me either.. :(
[Samsung Epic 4G Touch] kvevand63:
Just flashed v4-4.2 to E4GT/BeanStalk 1.330 via EL29. Yes, wifi does not work. Otherwise booted up with no other issued encountered.
[Samsung Epic 4G Touch] Zxo0oxz:
God, how did I **** that up. I'll fix it real quick.
[Samsung Epic 4G Touch] LucentBirch:
How long do you keep wifi on?
[Samsung Epic 4G Touch] jwhyte:
It's on all the time unless I an going to be away from wifi for a long time.
[Samsung Epic 4G Touch] LucentBirch:
See, I must always be around the wrong routers or something, because I have a ridiculous wlan_wake wakelock...
[Samsung Epic 4G Touch] jwhyte:
I get a crazy number too but doesn't account for much as long as your phone sleeps good when screen off. My wlan wake count right note is 54k but only. 9% battery used from it.
[Samsung Epic 4G Touch] Zxo0oxz:
http://f.the-beach.co/stuff/kernal/blasphemykernel-4-2-4.2.zip

Wifi fixed

Slqb enabled

Bfq enabled

Edit: this is still a test build but should be stable.
[Samsung Epic 4G Touch] LucentBirch:
I guess my Android OS is awake for a lot longer, so I don't understand how yours is only 7%...
[Samsung Epic 4G Touch] Krowbarr:
Working great sir:D:thumbup:

Owner/Operator Samsung E4GT running Pacman Rom w/Blasphemy v4 kernel.

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] jwhyte:
Mine always starts high then the more I use my phone it drops down.
[Samsung Epic 4G Touch] gamepro602:
Can you do this for 4.3?:)
[Samsung Epic 4G Touch] kvevand63:
Flashed v4-2-4.2 via EL26 to E4GT/BeanStalk 1.330. Thank you, wifi working. Running smooth, no issues so far. Question; any chance of incorporating frandom module in a future update? Again, much appreciation for your contribution, great job!
[Samsung Epic 4G Touch] ps3hacker3:
Woah wait where did you find the build 1.330? There's only 1.300 last I found
[Samsung Epic 4G Touch] jwhyte:
KT posted it in slim bean post #3 I believe.

Edit that's 1.300
[Samsung Epic 4G Touch] ps3hacker3:
Yea I just double checked it and it is on post 4 but its build 1.300 not 1.330
[Samsung Epic 4G Touch] kvevand63:
Sorry guys, typo on my part!
[Samsung Epic 4G Touch] ps3hacker3:
All is well mate just had me wondering
[Samsung Epic 4G Touch] jwhyte:
I just want to say great job on this kernel [MENTION=4210124]Zxo0oxz[/MENTION] I've been running this oc'ed to 1400 this evening about an hour and half screen on nonstop without a single glitch! Rock solid! Thanks!
[Samsung Epic 4G Touch] Zxo0oxz:
I'll look into it. However, that should be entirely user configurable, being that it could be potentially insecure.
[Samsung Epic 4G Touch] DEF3NDER:
I know this seems strange but after flashing this everything on the display seems slightly pixelated and jaggy, like if you turn up the sharpness on your TV too high. Has anyone experienced this before? Very strange.
[Samsung Epic 4G Touch] Zxo0oxz:
Only time I've seen that is when I tried Dirty Unicorns.
[Samsung Epic 4G Touch] jwhyte:
Some earlier versions of the ROM's had it I think it came from cm originally. I've seen it on Liquid thinking bridge a couple du. Shouldn't be anything kernel related.
[Samsung Epic 4G Touch] Zxo0oxz:
I'm working on a release that will include both.
[Samsung Epic 4G Touch] gamepro602:
OK I see then, want to get everything stable first
[Samsung Epic 4G Touch] Zxo0oxz:
Yeah, not to mention I don't have a good way to test 4.3. I'd have to download the ROM itself, and the kernel. This phone is my only Internet connection, and out here it can be so slow that a 6.5mb kernel can take 20 minutes to download from my build server.
[Samsung Epic 4G Touch] kvevand63:
Z... Update on v4-24.2; currently flashed to BeanStalk 1.300, 100/1400 hz, bfq/pegasusq. Running very smooth, however, encountered two random reboots (while opening Ti backup and settings) and two instances where my ext sd was not recognized/found after a reboot upon wiping cache/dalvik. Otherwise, device is running smooth with Crossbreeder and OKJ. Sorry no logcat, had it unabled during occurrences. Great job, I know you are a busy guy with your own busy life, but really apprecite you taking time out to contribute. Thank you!!
[Samsung Epic 4G Touch] Zxo0oxz:
Logcat doesn't do much for kernel problems anyways, in the future, after a reboot, pull a copy of /proc/last_kmsg, so I can take a look at it. On the other hand, I've had about one crash with this testing version so far. However, I can't tell if it's my kernel or the rom, because even with stock cm10.1, I had a few crashes of the same nature every few days or so.

Edit: forgot to post what I came back to this thread for.

How would you guys feel about using Aroma installer for configurable features? For example, somebody asked to implement frandom in this rom. However, for that to be of any use, I would have to include an init.d script to remove the stock RNG interfaces and point them to /dev/frandom. The two problems with that are: 1) I don't feel it's the place of a kernel to include userspace scripts/apps/whatever. 2) anyone that knows anything about cryptography will know that frandom is not high quality random data. While this most likely won't affect you unless you're generating SSH keys, encrypting your plans to bomb the white house, or possibly even generating bitcoin wallets on your phone, I still think it would be a much better option for it to be user configurable.

So, this is where Aroma comes into play. You install the zip in cwm, aroma boots up, 'hey, wanna use frandom as the system's random number generator? If you don't know why this is a security risk, it's safe to say that you won't have to worry about this and should probably use it.' Everyone gets a choice, everyone's happy.

Opinions? Note: frandom was just an example, this just opens up doors for other user configurable options.
[Samsung Epic 4G Touch] jwhyte:
Sounds good to me! Just be sure to include that if you are flashing from twrp aroma is a pain.
[Samsung Epic 4G Touch] deaver_92:
Aroma is fine with me
[Samsung Epic 4G Touch] gamepro602:
:thumbup:
[Samsung Epic 4G Touch] Zxo0oxz:
New builds posted:

What's changed from v4 test builds:

TCP Proportional Rate Reduction and a few other tweaks known to be stable re-integrated

frandom included, but not used by default. If you want to use it delete /dev/random and /dev/urandom and symlink /dev/frandom to it at your own risk

As with before, 4.3 is untested, use it at your own risk.
[Samsung Epic 4G Touch] deaver_92:
V4 booted and running smooth for the last 20 minutes. No issues so far.

Edit:

cm10.1 9/1 nightly

200/1400

hotplug/noop

frandom disabled
[Samsung Epic 4G Touch] Zxo0oxz:
Also, one thing I left out. I believe if you're using crossbreeder, it will automatically use frandom, so keep that in mind.
[Samsung Epic 4G Touch] kvevand63:
Flashed v4-final to BeanStalk 1.300. So far, running silky smooth. You out did yourself Z. Thank you for including frandom, will be trying a couple of frandom.ko modules to see which one will work. Crossbreeder works that much better with frandom (i.e Agats 1.42F for TW/E4GT). Btw.. my previous post regarding random reboots with v4-2 test release, they disappeared after I lowered read-ahead tweak from 4096 to 1024. Not sure if that was the cause, but it worked.
[Samsung Epic 4G Touch] LucentBirch:
What is frandom? Like, what does it do? I'm trying to understand more of how all this stuff works...
[Samsung Epic 4G Touch] gamepro602:
I installed the newest version with 4.3 and currently running illusion ROM, and ran into 3 problems

1- the hardware home key is not working, it isn't a hardware issue since I restored my backup and its working fine there

2-advanced settings for this device isn't sticking, its more noticeable if you disable the hardware lights, 30 seconds later, they turn back on.

3-data isn't working either, it says its connected but it doesn't work.

Other than that, its more stable than bedrock:thumbup:
[Samsung Epic 4G Touch] Zxo0oxz:
You will not need a .ko for frandom, as it's already built into the kernel as opposed to being modularized in frandom.ko...

Edit: if it's in module form (frandom.ko) you would need to load it with insmod, since it's built in, it's technically always loaded. You can tell it's loaded because it will create a "special file" called /dev/frandom.

It's just a replacement for the system's random number generator. It's much faster, but could be considered insecure under certain circumstances.
[Samsung Epic 4G Touch] Zxo0oxz:
Wow, as I said earlier "at your own risk", but if I have some time I'll take a look around...
[Samsung Epic 4G Touch] gamepro602:
Well I already knew the risk, just wanted to let you know.
[Samsung Epic 4G Touch] digitalmorphinex:
The home key in illusion is a ROM issue, not kernel..

No idea about the second one.. And the third, I had working data but its spotty until dastin is finished doing what he does best..
[Samsung Epic 4G Touch] gamepro602:
Well I didn't think the home button was a ROM issue because it worked when I was on the stock kernel, then again, it didn't work after I rebooted:what:
[Samsung Epic 4G Touch] deaver_92:
So what would I symlink /dev/frandom to?
[Samsung Epic 4G Touch] Zxo0oxz:
I'll make a flashable zip for it later, but for now it would be something like this:

mv /dev/random /dev/random_original
mv /dev/urandom /dev/urandom_original

ln /dev/frandom /dev/random
ln /dev/frandom /dev/urandom

If that doesn't work, I apologize. Just reboot and it'll be undone.
[Samsung Epic 4G Touch] thatdudepoops:
Yea but I had the same problem with the blasp final 4.3 with the home key...and a hanging up with phone calls...flashed blasp 4.3 solved the issues...same rom
[Samsung Epic 4G Touch] Zxo0oxz:
Wait, you got the 4.2 kernel to work on a 4.3 rom?