yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] JBTY:
I dont know if its coincidence but when i installed the hitman kernal w touch recovery i oced to 1700 and my battery died in about 5 hours. after that the Phone wouldnt boot normally. Tried flashing back to stock kernal w rougue recovery and my phone got Stuck in a bootloop. But at least i was able to get the old recovery back and full wipe everything and reflash the blend rom w stock kernal. Hope this helps.
[Samsung Epic 4G Touch] nibrwr:
I'm 99% sure he's referring to ROM Manager. There have been quite a few bricks using it to flash CWM Touch
[Samsung Epic 4G Touch] ReubenRene:
Does HDMI work with the gunslinger kernel? I connected my phone via HDMI to my television but nothing came on.
[Samsung Epic 4G Touch] GRBlitz:
Is there a way to use stock voltages without using Set CPU with the Hitman Kernel?? Blazer and Calkulin ROMs are a little laggy when flipping through the menus... Is there a stock voltage script that can be uploaded?
[Samsung Epic 4G Touch] meatwadathf:
Steady, love your work, but don't care for touch recovery.

Have you seen this thread? http://xdaforums.com/showthread.php?t=1509886

Your call man... your call...

EDIT: I guess they (sfhub) (http://xdaforums.com/showthread.php?t=1504808&page=20) figured out its the rom manager version only. Still, not a fan of Touch. lol
[Samsung Epic 4G Touch] greatlakesghost:
I honestly don't think your touch recovery is an issue. I have used it to install several roms and themes with zero issues. But if you feel its safer to pull it by all means. Obviously you have your concerns about the well being of everyone's phone in mind. Its better to wait for a safe and reliable product for the masses then to have something in question. While I like the touch recovery but I am just as happy with your modified version of regular cwm just as well, way less clicks to get the job done. ;)
[Samsung Epic 4G Touch] coiledwire:
Ever since the cwm issue with not wiping dalvik correctly back on the og evo, I've avoided it like the plague. I run gunslinger or your stock repacks since I feel more comfortable with the work done on rogue recovery.

The recovery is one thing that has to be 100% reliable 100% of the time.

Sent via EM waves.
[Samsung Epic 4G Touch] Anon9mouz:
So is it the touch cwn not the modified hitman but just cwm touch or rom manager that's causing bricks. Bc i been trying to try it but everyone keeps saying it's buggy or what not
[Samsung Epic 4G Touch] meatwadathf:
Supposedly its the rom manager one since it is technically a "fake flash" according to sfhub, and it conflicts with the linux kernel.

Try it out if you want. I did. It was annoying as hell having to scroll through 15 laggy options to do anything so I went back to a rogue recovery.
[Samsung Epic 4G Touch] ryandoubleu:
problem

Ok so I have been using your "rogue gunslinger" for awhile but whenever I flash "hitman" and boot back into my ROM, after waiting awhile (maybe 1 hour or 2) and boot into recovery, it boots to CWM 5.8.1.5. When it boots to that recovery it continuously boots to it not allowing user control even after doing a battery pull. The only way to get out of it is to hit the home button a whole bunch of times, then it will eventually boot back into the ROM. I then was able to use the autoflash tool to put gunslinger back on.

I have verified this issue by reproducing this problem several times. Not really sure what to do from here but will stick with gunslinger til some sort of resolution is found
[Samsung Epic 4G Touch] Shoulon:
Nevermind.
[Samsung Epic 4G Touch] xjs1200x:
Any idea why odin .tar file freezes odin?

i get :

<OSM> Check MD5.. Do not unplug cable..

<OSM> Please wait..

Freeze....
[Samsung Epic 4G Touch] mavd5831:
Bad download, download again.
[Samsung Epic 4G Touch] xjs1200x:
Ive downloaded 4 or 5 different times haha. It either gives me that error ^^ then freeze

or it says something about the md5 hash being invalid then freezes. qbking thinks its the cable.

But i just put it on my sd card and flashed. worked fine. thnx
[Samsung Epic 4G Touch] JohnCorleone:
Ok, Ask anyone who knows me. I am totally unbiased and test everything. Was running 1600/200 on demand last night and it was amazing. Today, I went to stock settings and I was receiving emails and G-Talk messages simultaneously and had 3 or 4 soft reboots. The recovery is INCREDIBLE though
[Samsung Epic 4G Touch] jaysmi32:
its at 1450mv, what do u recommend?

---------- Post added at 10:46 AM ---------- Previous post was at 10:09 AM ----------

also what's the hightest voltage u can run on this phone?
[Samsung Epic 4G Touch] toprock23:
Well I have no problems running 1400mv. Also, Check ur battery temps. I personally wouldn't go over 1475mv. Don't worry if u can't get it that high. Not all chips are the same.
[Samsung Epic 4G Touch] sportsplayer5959:
Smooth as butter my friend! You seem like a pretty cool guy. Thanks for your work!

GO HAWKS!!
[Samsung Epic 4G Touch] dre2phresh:
My new favorite kernel! It works well with Calk's rom. The only I've noticed is when using the init.d scripts, it changes the governor from conservative to ondemand. I use Rom Toolbox to check cpu changes.
[Samsung Epic 4G Touch] Duce HD2:
Yeah my phone is the same way....I get about 1 benchmark at oc'd at 1.6Ghz set on performance then freezes/ reboots, all that fun stuff...oh well, doesn't bother me. At 1.5Ghz it's stable though.

Very nice kernel btw!

Sent using Calkulin's V1.1
[Samsung Epic 4G Touch] Steady Hawkin:
It shouldn't change. I modified Calk's script to not detect Android Overclock so I can watch the gov/scaling on the widget. It runs all of his presets during my testing on it, including the governor. Keep in mind if you have most overclock apk's installed (SetCPU, Android Overclock, etc) it will over ride his scripts.
[Samsung Epic 4G Touch] xxxicu812:
Did you wipe anything before flashing? If so which ones?

Thanks in advance
[Samsung Epic 4G Touch] dre2phresh:
All presets work fine just the governor changes. No overclock apk's installed just Rom Toolbox. So I don't know why it changes then.
[Samsung Epic 4G Touch] sockey:
Not sure what you mean by home screen lag... when I push the power button to wake the phone up it takes a while to see the lock screen, but after that there is no lag. Does this kernel get rid of the wake up lag?
[Samsung Epic 4G Touch] greatlakesghost:
I havent had time to check this but will test it tonight. I will let you know what I find.
[Samsung Epic 4G Touch] greatlakesghost:
I have always had lag after wake up but not as you described but when I go to start scrolling from homescreen to homescreen. For some odd reason I never have had the wake lag that others describe from having an sd card in, just the homescreen lag.
[Samsung Epic 4G Touch] distantneighbor:
Can I flash this over Stevestrong's odexed themed eg30 rom?
[Samsung Epic 4G Touch] xlGmanlx:
This is a kernel and recovery yes. They won't be impacted by odex or deodexed
[Samsung Epic 4G Touch] jaysmi32:
Which oc program are u guys running to get 1.5ghz?
[Samsung Epic 4G Touch] xlGmanlx:
Personally I am running SETCPU
[Samsung Epic 4G Touch] ebuechler3:
thanks.. whats the best setup for setcpu with Rouge 1.1.1 on calks? i have 200-1000 min max conservative, profiles=sleep 500-200, and i changed a few things in voltages= 1000 mhz to 1050 mv.. and from 800 mhz to 950 mv. 500 mhz to 900mv, 200 mhz to 850 mv..... is this the best setup if i want the best battery life with decent speed or is there more that i can do? i would manually take out those superfreeze apps, but i cant figure out which one kills my battery when i take em out so im gonna leave those superfreeze apps (media hub, sns, etc) in my rom for now
[Samsung Epic 4G Touch] jaysmi32:
Does setcpu support 1.5ghz? I only see 1.4 and 1.6!
[Samsung Epic 4G Touch] sleshepic:
Flashed this kernel and really liked the recovery setup, but my phone acted a little funny running on the kernel. My phones normally nice and stable OC'd at 1.6, but benchmarks were worrisome on this kernel at 1.6. Was only getting 3300-3650. I know benchmarks aren't everything but they can be at least an indicator, rom toolbox, android assistant and quadrant all force closed as well. Flashed back to lostkernel 1.0.0.8 and got 5000+ on benchmarks again, weird. Will def try when newer version comes out, like the recovery.
[Samsung Epic 4G Touch] Dj21o:
Is anyone having problems with UV values not sticking? I am using voltage control and they just go right back, even if I select it to save as boot settings. Should I use a different app?

Sent from my Galaxy S II.
[Samsung Epic 4G Touch] ryandoubleu:
....

if you flashed hitman from the rogue gunslinger recovery, I would advise you to revert back to gunslinger. The temp flash gets screwed up and may brick your phone if you didn't use odin to flash the recovery
[Samsung Epic 4G Touch] Steady Hawkin:
Alright bro, please check the facts before you spread false information. I do not take nicely to anything that relates to bricking, or an unsafe release. Flashing 'Hitman' from a real recovery is NOT a fake flash. If you flash Koush's touch recovery from Rom Manager, that is a fake flash. Please keep the two separated!

IMO no one should be flashing any recovery from Rom Manager period, at least until the issues get cleared up.
[Samsung Epic 4G Touch] Duce HD2:
Don't even need to OC this kernel, fast and smooth as hell as it is. Nice work as usual.
[Samsung Epic 4G Touch] greatlakesghost:
I agree with qbking. Definitely try another cable. Have had it happen to me more than once.
[Samsung Epic 4G Touch] xjs1200x:
Just by watching QBking's video I flashed the kernel via rogue recovery. And now the Clockword Mod touch recovery is on there, i guess be default.

but no issues.

But then i saw the a new ROM out, and well of course flashing the new ROM put me back on the kernel that comes with the ROM.
[Samsung Epic 4G Touch] ryandoubleu:
OK bro, I flashed hitman several times from gunslinger and kept having an issue with the cwm touch 5.8.1.5. I pm'd you and received no reply. You want a video, I can make one to validate what I said. If you don't want to believe me that's fine, you will just have to get over yourself

Also, I never have used ROM manager and it was never inferred that I did.

---------- Post added at 04:14 PM ---------- Previous post was at 03:30 PM ----------

Also, why don't you explain why if you hit one of the volume buttons or power button or menu button the cwm touch recovery resets to the initial menu?
[Samsung Epic 4G Touch] Steady Hawkin:
1) The recovery version is 5.8.1.5 as clearly listed in the OP

2) Your PM asked why when you press buttons the recovery rests itself. Its a touch recovery and that question has been answered a million times in this thread already. There is also a video of the recovery attached to the OP.

3) Good news, I just got "over myself"

4) WE did not build the recovery, Koush did. Perhaps you should shoot him a PM and ask why he designed it that way;)
[Samsung Epic 4G Touch] coiledwire:
I still don't understand why there's any negative vib here. If someone has a problem with how the dev works or requests, just quit using the goods and make one yourself. Why argue? :confused:

Steady et al, I continue to appreciate the work here, but maybe the touch recovery should be pulled until you guys can put the rogue stamp on it. Seems alot of drama is here because of koush's work.

Sent via EM waves.
[Samsung Epic 4G Touch] meatwadathf:
Agreed....
[Samsung Epic 4G Touch] sputnik767:
I agree. From what I can tell, it does not seem that there were any issues with bricked devices such as what some are currently experiencing until Touch Recovery. At the very least there should be a warning in the OP, so people know the risks. I'm not sure if anyone knows the exact culprit for the problems, but it does seem like touch recovery is implicated in some way.
[Samsung Epic 4G Touch] JBTY:
I also agree. you should pull it until it's white and green and says rogue lol
[Samsung Epic 4G Touch] dgn_sandibalz:
I am one that bricked my phone. It was definitely not this version that did it. In fact I had no issues while using this version.

I did not use rom manager though. I flashed the temp recovery through the stock recovery. But, that isn't what did it.

The brick happened when I used the temp recovery to factory reset and wipe all. When it tried to wipe data it borked the partition structure. Tried repartitioning with Odin, No go. Tried using PIT file, No go. Phone wouldn't boot past black screen and gave a No data partition error in recovery.
[Samsung Epic 4G Touch] Anon9mouz:
I flashed the regular 5.0.2.7 cwm from rom manager it was golden its on my miui back up and seems to work just haven't tried the touch or yours would like to but all I hear is buggy can u clarify for me bc i wanna use ur hitman bro:D

__________________________________________________
[Samsung Epic 4G Touch] nibrwr:
Not to speak for SH but... my personal experience with Hitman was smooth. The kernel is the same as Gunslinger, so you get the great performance. I didn't like touch recovery and prefer the Team Rogue recovery to all else.

99.9% of all Touch recovery problems come from flashing stock CWM Touch, whether from ROM Manager or something else
[Samsung Epic 4G Touch] Anon9mouz:
O ok so if i use hitman Odin it instead of flashing well i think I tried to do that a few days back but none of the tar links were working idk check and see if all his links r working

__________________________________________________
[Samsung Epic 4G Touch] nibrwr:
Are you having trouble flashing? I used the zip file
[Samsung Epic 4G Touch] meatwadathf:
To clarify, if you MUST use the touch recovery, the safest method is to use a version which is bundled with a kernel (like the hitman). It does NOT matter whether you flash the zip hitman or odin hitman.

The problems arise when you flash the touch recovery as a standalone recovery, whether through rom manager or any zip/tar released by Koush (cwm dev).
[Samsung Epic 4G Touch] Custodian:
The links were pulled... where can I download Zhua kernel
[Samsung Epic 4G Touch] mavd5831:
That's what happens when people accuse without knowing just wait for them to come back up.
[Samsung Epic 4G Touch] tdunham:
I would like to get the Tar version as well. Also, are there any links to prior versions?

Edit: Sorry I'm blind, there are links still on the OP.

All this talk about problems with CWM.

I was under the impression that Rooting and then installing CWM was the standard thing to do. If we could root, then Odin a stock (Rogue) kernel with recovery built-in, wouldn't that be a better way to go? (I don't feel like flashing back to a stock rooted rom to find out if it would work)

I haven't had any issues with CWM along with Rom Manager yet but I thought I that there were entire threads dedicated to warning people about the dangers of using Rom Manager.

In other words, what is the recommended way to install/implement recovery?
[Samsung Epic 4G Touch] digweed4me:
We need to get steady back let's donate he might come back
[Samsung Epic 4G Touch] coiledwire:
I'm still familiarizing myself with samsung versus HTC. But from everything I know up to now, for the e4gt the kernel and recovery are located in the same partition. So the best method to getting a recovery is to use a kernel/modem combo and install with either odin or flashing via existing recovery. Personally, I'd avoid rom manager for recovery.
[Samsung Epic 4G Touch] tdunham:
I only use Rom Manager to create a quick backup. I reboot to use the Rogue recovery if I need to do anything else like a wipe or restore. Is that alright or should I get rid of Rom Manager altogether? I guess I don't understand the dangers of using rom manager...
[Samsung Epic 4G Touch] coiledwire:
I'm not the know-all source for this info. But I do know that we all depend on the recovery to always work. I would limit the chances of bad things happening, this would include using a different recoveries to backup and restore. As I've stated before, cwm left a bad taste when it messed up dalvik wipes on the og evo. So I avoid cwm and rom manager if at all possible. I've had nothing but positive experiences with anything the rogue team made themselves and shared with us.

Could something get messed up with rom manager's backups? Maybe yes, maybe no. Would I ditch using rom manager? Definitely yes. Would I solely use rogue recovery for everything? Hell yes.

This is my personal, biased opinion. YMMV.

Sent via EM waves.
[Samsung Epic 4G Touch] mavd5831:
If you really need rogue and don't want cwm touch or are scared of using it just download gunslinger 1.4.1.....same kernel just standard rogue recovery.
[Samsung Epic 4G Touch] tdunham:
Ahh, now THAT makes perfect sense to me :)

Thanks Coiled for the input.

---------- Post added at 02:45 AM ---------- Previous post was at 02:42 AM ----------

I did try Hitman and the touch recovery was kind of nice but it takes a little getting used to. I ended going back to 1.4.1 because it was easier for me to figure out LOL.
[Samsung Epic 4G Touch] JohnCorleone:
Exactly. Gunslinger 1.4.1 has Voodoo Louder support and I have used it on several different setups. I imagine Steady pulled Hitman because why would he want to be blamed or have his reputation tarnished because the touch recovery may have issues. Rogue kernels are baked into so many ROMs now so they are proven. Some prefer stock repack some prefer the extra muscle built in. Both have the Rogue streamlined recovery.
[Samsung Epic 4G Touch] imakul8:
Thanks for clarifying..I been looking for a Hitman link throughout today. I couldn't find a link anywhere.:confused: I was about to ask someone to PM me a link.:p I thought maybe it had other benefits besides the touch interface..although I would like to try it..but, I'm very happy with Gunslinger. :D
[Samsung Epic 4G Touch] mavd5831:
No worries =}
[Samsung Epic 4G Touch] Admiral2145:
Mistake

I flashed calk 2.91 rom and flashed hitman b4 I rebooted the phone. Now when I try to go into recovery it sits 1 second then reboots back into the rom... What should I do so I can get back into the recovery? TIA
[Samsung Epic 4G Touch] mavd5831:
Try reflashing a stock .tar with Odin and then flash calk then reboot.and flash hitman
[Samsung Epic 4G Touch] Admiral2145:
stock kernel tar or stock rom tar? im new to the e4gt, had this phone less than a week...
[Samsung Epic 4G Touch] tdunham:
You probably have 2 different recoveries already installed.

If you hold the pwr key for a couple of secs, the recovery shown there will bring you to Hitman. (PWR/Vol Up while rebooting does the same thing)

Since you already have Rom Manager installed, you can boot into the basic CWM recovery from there.

I would try reflashing a different kernel, maybe gunslinger then try hitman again. It's always possible your hitman download got corrupted too to begin with.

Edit: Oh, and as Mavd5831 stated above, you may have to use Odin. Odin is your friend and you should get familiar with it!

FYI, Odin works with Tar files, CWM/Rogue recoveries you can only flash Zip files.
[Samsung Epic 4G Touch] Admiral2145:
fixed it

thx everybody I got it working had to reflash like I re-rooted phone and got the recovery back
[Samsung Epic 4G Touch] Custodian:
Case you're wondering. I find On demand governor and sio I/O scheduler to be better for our phone.
[Samsung Epic 4G Touch] lawslb15:
wheres the download link?????

I clicked the source and it brought me to another page and I cant find the download link the page is very confusing

anybody have a direct link?
[Samsung Epic 4G Touch] mavd5831:
I believe links were pulled. And unless you ask Steading Hawkin for permission I won't post the kernel. Its up to him since he is the owner/creator of it.
[Samsung Epic 4G Touch] JohnCorleone:
I concur sir
[Samsung Epic 4G Touch] dw3bb10:
I tried running this with Blazer ROM, any idea why when using on demand, it will clock alot at 1.2ghz when it doesnt need to....Doesnt do that on the Rouge repacked kernels....also, how far do you guys Undervolt?! I need some recommendations to extend my battery life!!! Thanks!
[Samsung Epic 4G Touch] interloper:
Since the governors are created to respond to their respective impulses I say your phone is demanding the CPU to ride high based on a process in the background. Use the applications menu to see processes using high memory and look at whats eating your battery. That process will be the culprit. I agree that on demand works well for this device. Good luck.
[Samsung Epic 4G Touch] Admiral2145:
lazy governor

what does the lazy governor do on the e4gt? I search and cant find a description about it
[Samsung Epic 4G Touch] meatwadathf:
Not much...
[Samsung Epic 4G Touch] b0ricua:
I've noticed in the "E4GT General" forum that people are bricking their phones when going from an ICS back to a GB ROM using a "touch" recovery. Are there any anticipated issues with using this version of touch recovery going to/from various ROM's/Builds?

Any help would be appreciated, I'll roll back a version if things are dicey.
[Samsung Epic 4G Touch] mavd5831:
Touch from rogue is fine just dont flash the touch from rom manager cause you will die.
[Samsung Epic 4G Touch] sputnik767:
There still seem to be a lot of questions as to what's causing all of these issues. It seems that if you are going to go to ICS, you should ODIN the ROM and the custom kernel if you choose to use one. Then, if you want to go back to GB or restore a GB nandroid, definitely ODIN back to a GB rom and reinstall the GB kernel. Having said that, I have seen reports of people bricking their phones seemingly by simply wiping partitions with touch recovery and flashing roms the normal way. I guess the point is this: touch recovery definitely seems to be implicated in bricking the devices in some way and running it is a huge risk for the small convenience of having a touch interface in my opinion. I'm here because I bricked my og Evo using a touch recovery. Also, the current ICS roms may not be playing well with any current recovery, just based on some of the things I read over in the bricked thread in one of the other subforums.

So to summarize, this is what I personally believe: absolutely stay as far away from touch recovery as possible for the time being because the small convenience is not worth the apparent risk. Therefore if I were you, I would not flash any roms from touch recovery and would not do any sort of wipe from it either. Revert back to the older version if you want to play around with GB roms. If you want to try ICS (except CM9), stay away from any recovery except for the one that comes installed when you ODIN. The current FB builds are experimental, and I'm not sure that the non-touch CWM recovery has been tested with or even designed for ICS. Point is, if you are going to run any of the FB leaks, do ODIN only and keep the stock recovery until the official ROM is released and a proper recovery is developed. Plus you get the added benefit of not having your flash count increased by using ODIN to install the custom recovery to the FB leaked builds.
[Samsung Epic 4G Touch] Custodian:
Ondemand best govenor for our phone.

Scheduler:

sio>deadline>noop>cfq> etc....
[Samsung Epic 4G Touch] AVAH0LIC:
Alright over the past few months I've learned soooo much and have a pretty good understanding of how this phone works, now what is this governor you speak of lol. I'm sure its pretty much just like it sounds.

More importantly are these flash able or do you edit scripts? Any info is greatly appreciated. And btw I'm on the app, we all know how terrible the search is :/

Epic 4G Touch perfected by Calk!
[Samsung Epic 4G Touch] pandamaja:
Agreed, safest way is to Odin back to stock, start over.
[Samsung Epic 4G Touch] nitronet:
I'm using hitman and love the touch recovery works flawlessly with calks rom.
[Samsung Epic 4G Touch] b0ricua:
Great insight, I appreciate your input. I'd love to hear what Steady Hawkin has to say about this subject...