yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Slobadon:
I started to get the random phone off thing also, running project-X 2.0 and then installing agat 1.4. Glad I wasn't the only one (well only sorta glad, more like relieved). I uninstalled CB 6.18 to narrow it down. Still had phone off problem so I started to disable all of the power/battery saving tweaks and options since I thought it may just be going too far into a deep sleep or something. I came back here and just now read about this issue, So now Im back on agat 1.3 after flashing the .zip. I'll report back if I still get a phone off problem.

edit- I had first dirty flashed Project-X 2.0. (which is stated as an OK method) Just for the heck of it I did the JB 2X wipe zip and reflashed a clean Project-X 2.0, booted then flashed 3minit settings. Ive done nothing else. Project-X comes with Agat 1.3 so I'll see how it runs for a day or so for me before I do any more tweaking.
[Samsung Epic 4G Touch] helix4u:
The interactive gov also causes hangs just like adaptive. I'd not recommend putting it back in.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
[MENTION=1528277]agat[/MENTION],

If you saw my post, ignore this. I had the problem both with and without CB flashed. Haven't had it again since restoring 1.30.
[Samsung Epic 4G Touch] btvolta:
I guess I'm very luck because I am on Project X 2.0 with Agat's 1.4.1 and Crossbreeder 6.20.13 and haven't had one issue.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
How long?
[Samsung Epic 4G Touch] btvolta:
I've been on 1.4.1 ever since he updated to it, and I was on Crossbreeder 6.19.13 for a couple of days and now 6.20.13 since early this morning.
[Samsung Epic 4G Touch] Slobadon:
Very lucky!
[Samsung Epic 4G Touch] btvolta:
Guess what? I spoke to soon, i locked up.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] remotehugger:
yea, I've had to go back to 1.3 -

from jdsingle's deodexed ROM w/ agat63's 1.3.0 kernel - with TT 2
[Samsung Epic 4G Touch] Slobadon:
serves you right! Just kidding, I was really pulling for you.
[Samsung Epic 4G Touch] btvolta:
I just flashed back to 1.3. Does anyone know if we can use the crossbreeder 6.20.13 with 1.3? I know 1.3 doesn't have framdom molecule.
[Samsung Epic 4G Touch] blackcanopy:
Us you can use Agat 1.3 kernel with the latest 6.20.13 CrossBreeder. It doesn't have frandom modules either... :D
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I know it's moot now, but I thought 1.41 just came out yesterday? :)
[Samsung Epic 4G Touch] gamepro602:
It did just come out yesterday
[Samsung Epic 4G Touch] jt_hatch:
Just had a SOD with 1.4.1 after uninstalling CB (flashed the CB uninstall zip in recovery) -- so, same setup as I was running 1.3 since it came out w/o issues hung on 1.4.1 within hours... sad to say it does look like something in the kernel.

Game to be a test monkey on a 1.3 + frandom build. if you have time and are so inclined to make it... I got pretty hooked on the frandom+CB boost in the short time I had it. :good:
[Samsung Epic 4G Touch] helix4u:
Check out https://github.com/agat63/AGAT_GB27_kernel/blob/master/drivers/cpufreq/cpufreq_conservative.c for your min sampling rate on conservative gov issue... I believe the min is there by design.

BTW, been running all last night and all day and still can't get this thing to freeze up on me. What else are you guys running besides 1.4.1 and crossbreeder that could be causing the SOD issues? Any other tweaks or apps in common with each other? What Rom, etc?
[Samsung Epic 4G Touch] remotehugger:
I was running jdsingle's deoedexed ROM with no other mods or tweaks -

from jdsingle's deodexed ROM w/ agat63's 1.3.0 kernel - with TT 2
[Samsung Epic 4G Touch] helix4u:
So that's a GB28 rom with a GC01 preload partition + removed apps... that's kinda neat.

I'm on Kobridge's deodexed 'stock" rom with Kobridge's 4.34A tweak pack, silent camera mod, patched email mod, all in one mod, crossbreeder, and I believe that's it. But no SOD yet.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
What CPU, Governor and Scheduler settings, Helix? In my case I've had 25MHz-1.3GHz, tried Conservative, OnDemand and PegasusQ with both NoOp and SIO. No undervolt.
[Samsung Epic 4G Touch] helix4u:
standard 200 MHz - 1GHz pegasusq/sio. I'll try a larger spread/ other governors/schedulers
[Samsung Epic 4G Touch] agat63:
Here we go:

AGAT_GB27_v1.4.2F.tar this is same is v1.3.0 (linux version 3.0.75) with frandom module.

AGAT_GB27_v1.4.2.tar Linux version 3.0.82 and no frandom module

This way we will know what causes the freezes and SOD's.

Updates to Linux 3.0.82 or adding the Frandom....

Let's the testing begin...
[Samsung Epic 4G Touch] gamepro602:
Making a backup, will report back in an hour or two...
[Samsung Epic 4G Touch] Doctor_XXX:
Got two freezes/lock ups on the 3.0.82 version, none (so far) on the 3.0.75 version. Yes, I've only been testing for an hour or so, but at least it is a data point, right? Will repost if 3.0.75 version gives me any hiccups, or continues to run nicely like v1.3.0 did. :beer:
[Samsung Epic 4G Touch] agat63:
Since you guys are in testing mood here couple more kernels to test :D

AGAT_GB27_v1.4.3.tar Linux version 3.0.83

AGAT_GB27_v1.1.3F.tar Linux version 3.0.83 with frandom module.

Wile I was fooling around with my 3.0.82 kernel new update to linux version popped up.

Hopefully this update is fixing whatever problems we had with previous Linux version.

Good luck.
[Samsung Epic 4G Touch] gamepro602:
I tested each one of the kernels for about an hr (3.8.2) the one w/o the module was the smoothest for me with no lockups, the other one worked OK but it was a bit jittery and it crashed my launcher, but after letting it settle for two min. Every thing is good, no lockups or malfunctions here, going to test the new kernels now
[Samsung Epic 4G Touch] blackcanopy:
Are these not mobile Odin compatible? I tried using Mobil Odin to flash 1.1.3F (which I believe should be actually 1.4.3F) and checked the box to wipe dalvic cache, but it didn't go thru the "android upgrading" screen and in the system/about device screen still shows Linux version 3.0.82 Agat 1.4.1.

Edit: and seems to be the smallest in size at 5.4mb compared to your other kernels. I know it shows 5.5mb on the download page, but mobile Odin sees it showing 5.4mb. Downloaded twice and flashed both twice using Mobil Odin with the same results.
[Samsung Epic 4G Touch] gamepro602:
It flashed fine for me and I'm using Mobile Odin lite
[Samsung Epic 4G Touch] blackcanopy:
I moved the files to the root internal SD (instead of in a folder on internal SD) and unchecked the wipe dalvic in Mobil Odin and it flashed fine.
[Samsung Epic 4G Touch] Stryke_the_Orc:
FWIW, on every kernel that includes the frandom module, I've had freezes when phone enters deep sleep. I have had, and kept, crossbreeder installed. After work I'll uninstall and test theory that it's the script:thumbup:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] roirraW "edor" ehT:
SOD on 1.43F (Frandom), no CrossBreeder flashed. Only had the kernel on there for less than half an hour. I do and always have used DS Battery Saver, BTW, but don't normally have any problem waking the phone.

Just rebooted, flashing 1.43 without Frandom to test.

Edit: no problems yet!
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Well bummer. I just pressed the power button, the screen woke up but everything was frozen. I was able to turn the screen back off with the power button but now it's SOD. I'll try 1.42 with Frandom next.
[Samsung Epic 4G Touch] helix4u:
Guess I'll throw 1.4.3F on, but I'm still not getting the freezing/SOD results anyone else is (in my whole 10 minutes of running 1.4.3F, :laugh:). Do you guys have connection optimizer on or anything like that?
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Just DS Battery Saver here, never ever EVER use Connection Optimizer and any new stock ROM-based install I'm paranoid enough to check twice to make sure Connection Optimizer is off. LOL. The same setup is always fine with me once I go back to 1.3, even if I'm only flashing the kernel, not doing a full restore of a backup.

But I'll see what 1.42F's doing, without flashing CB for now - so far fine.

Edit: Still good!
[Samsung Epic 4G Touch] leaderbuilder:
Only time I've gotten sod is when I've had crossbreader installed. Tried the 143f with it last night and somewhere on the middle of the night it sod'd.

Removed crossbreader, still on 143f, and will run today see how it goes.
[Samsung Epic 4G Touch] gamepro602:
Flashing 1.4.3F gave me a lockup on start up and then I got a bootloop
[Samsung Epic 4G Touch] Stryke_the_Orc:
Looks like it's the combination of frandom module and crossbreeder that caused the SOD in my case. I only had 1.4.3f flashed for three hours and when phone went into deep sleep it wouldn't wake again. Have had 1.4.3 installed since 8 am with no issues:thumbup::beer:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] gamepro602:
Yea I'm running 1.4.3 right now and there's no issues to come by :)
[Samsung Epic 4G Touch] helix4u:
See that's just weird because I've been running 1.4.3f for a bit now with crossbreeder, have had it in and out of deep sleep a bunch with no issues... Is there anyone else that has installed these builds with no issue or am I just extra special? :D
[Samsung Epic 4G Touch] remotehugger:
just installed 1.4.3f - very long boot time - had to re-grant some SU permissions ( Ti, RTB, SDmaid ) just running jd's stock deodexed ROM with no tweaks or mods - gonna run the for a bit then flash crossbreeder and see how it goes - will keep y'all posted !

from jdsingle's deodexed ROM w/ agat63's 1.3.0 kernel - with TT 2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Still 100% on 1.42F without CrossBreeder flashed. I'll flash CB when I don't need my phone later.

Edit : by now I've forgotten whether I have F or not F flashed.
[Samsung Epic 4G Touch] remotehugger:
also still good on 1.4.3f - ran quadrant a few times and still no freeze ups or anything - gonna let it go overnite and if all is well will flash crossbreeder tomorrow - :D

from jdsingle's deodexed ROM w/ agat63's 1.3.0 kernel - with TT 2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Is this with Frandom or not?
[Samsung Epic 4G Touch] agat63:
Should be with frandom.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Thank you, sir! I'll go ahead and flash CB now then.

Edit : no SOD with 1.42F and CB flashed yet!
[Samsung Epic 4G Touch] Doctor_XXX:
I've been running 1.4.3F *AND* Crossbreeder for quite a few hours today...NO LOCKUPS or other strange behavior. I'll let it go tonight and check it again in the morning. :laugh:
[Samsung Epic 4G Touch] Samsung Fanboy:
Been running for 7 hrs no problems! I am also uv.

Sent from my Cross Breed V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] agat63:
Since I posted few test kernels would you please specify which one are you running.

It will help me and others as well.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Still no SODs overnight with 1.42F and latest CB flashed.
[Samsung Epic 4G Touch] ardianz:
On ko rom+cb20.6+ko tweak aggresif+pegasusq,sio+aio v4+kernel 1.43F,have freeze once when browsing using chrome...no sod when deepsleep..

thx

===

I dont known if aio make influence...coz i used aio v4 size 53,46mb...when i check aio thread,aio v4 size file change became 43mb and i dunno what different about that two file
[Samsung Epic 4G Touch] Samsung Fanboy:
I will also add running the latest CB and V6!

Sent from my Cross Breed V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] remotehugger:
been running 1.4.3f with crossbreeder 6.20 since last nite with no hiccups yet - :D

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] btvolta:
I've been running 1.42f with crossbreeder since last night without problems.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] agat63:
If no one did encounter any problems with 1.4.3F may be I can update the thread and post it in OP?

What do you think guys?
[Samsung Epic 4G Touch] gamepro602:
Did you install the kernel first then CB or did you have CB installed prior to flashing the kernel?
[Samsung Epic 4G Touch] remotehugger:
I have been installing kernel first - putting phone through some bench's and stuff - then crossbreeder and doing some more stressing - [MENTION=1528277]agat[/MENTION] - I've been running it since yesterday with no problems - I'd say yes, but then again I'd hate for you to do that and then have something happen - lol

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] agat63:
Worse that can happen will be some users having freeze ups and/or SOD's.

I can wait for another day. That's not a problem.

If no one reports problems with 1.4.3F till tomorrow I'll post it in OP.
[Samsung Epic 4G Touch] gamepro602:
You might want to say that uninstalling any tweaks or mods is recomended before flashing, as my lockups were caused by having CB installed prior to installing the kernel
[Samsung Epic 4G Touch] agat63:
Good point.

Thanks for suggestion.

I'll add that info to OP when I post the kernel.

Since I'm not using the phone I heavily rely on info and test results from you guys.

Any bit of information helps..

Thanks to all of you for testing and helping me.
[Samsung Epic 4G Touch] blackcanopy:
And thank you for your continued support. Can't say enough how much it's appreciated.
[Samsung Epic 4G Touch] CyberpodS2:
+1 Thanks Agat!
[Samsung Epic 4G Touch] btvolta:
Is this the 1.43F?

Edit: It is, it just threw me since it says 1.1.3F.
[Samsung Epic 4G Touch] remotehugger:
son of a "beep" --- just had to hard boot - phone wouldn't wake from sleep - knew I shod of just kept quiet - lol - gonna keep running it and see if it happens again - dang it !:banghead:

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] btvolta:
Maybe we should just stay on 1.42F since I was on it since yesterday and havent had any problems. And I already had CB 6.20 loaded and didnt uninstall prior to flashing 1.42F.

---------- Post added at 07:32 PM ---------- Previous post was at 07:24 PM ----------
[Samsung Epic 4G Touch] svicenty:
Post it
[Samsung Epic 4G Touch] cramer18:
1.4.2f

been running 1.4.2F with crossbreeder 6.19.13 and directinject 1.0.3 for over 24 hrs on jellyverse 3.0 and have not had any issues at all. installed crossbreeder and directinject after installing 1.4.2F. oc at 1500/300 with cfq i/o and pegasusq gov.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I thought that 1.43 both F and not caused problems for some people, including me. 1.42 (still not positive if F or not) is the only one which hasn't caused any problems for me.
[Samsung Epic 4G Touch] remotehugger:
just had to hard boot again - I just don't get it -

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] Samsung Fanboy:
Update from my last post I still have no problems what so ever. I have V6 and CB installed. I am also on smartassv2 with I/O sio schedulers. 200 mhz min 800 mhz max and under volted. 1.4.3f kernal.

Sent from my Cross Breed V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I'm trying 1.42 (not F) just to test and so far it's more responsive than with the F version.
[Samsung Epic 4G Touch] gamepro602:
Thats the one im running now, it had the best "feel" and 0 problems
[Samsung Epic 4G Touch] btvolta:
I ran 1.42f for a day and half without any problems. I tried 1.43f yesterday and when I woke up this morning, my phone was sod, also I noticed that it didn't want to go in to deep sleep mode, better battery starts showed it staying awake more than anything else. I just flashed back to 1.42f.

Sent from my SPH-D710 using Xparent BlueTapatalk 2

---------- Post added at 08:10 AM ---------- Previous post was at 08:06 AM ----------

Did you sod over night?

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Nope, 1.42 (non F) running strong!
[Samsung Epic 4G Touch] btvolta:
I do well with 1.42F but I sod'd overnight with 1.43F. It looks like the best kernels are the 1.42 series, F & non F.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] blackcanopy:
I believe the only difference in the 2 (1.4.2 and 1.4.3 series) is the updated Linux in 1.4.3.
[Samsung Epic 4G Touch] btvolta:
Could that be the issue?
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Actually, 1.42 has updated Linux and 1.42F has old Linux but with Frandom. 1.42 (non F) SOD'd on me now so it looks like it's the Linux. I'm back to 1.30 for now since I like it the best overall.
[Samsung Epic 4G Touch] blackcanopy:
I must have mis-read post number 511 then?...

http://xdaforums.com/showthread.php?p=42792112
[Samsung Epic 4G Touch] btoddweber:
Just so you know I purposely have tried to let my phone go to sleep to see if I get stuck...and so far nothing bad has happened. Wakes up like supposed to.

Jellyverse 3.0 with Comadose 1.4 with Crossbreeder (was installed prior while on Garwyns 5.0) just mobile Odin tar
[Samsung Epic 4G Touch] btoddweber:
Flashed it as soon as I took phkne off charger so battery time is same as run time for kernel
[Samsung Epic 4G Touch] roirraW "edor" ehT:
That's version 1.43, not v1.42. Look earlier only a little.

So which kernel and version now?
[Samsung Epic 4G Touch] btvolta:
According to this, 1.4.2f is the same as 1.3 but has frandom added. This has been the best for me.

http://xdaforums.com/showthread.php?p=42789513

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] blackcanopy:
That was my point.. I believe he took 1.4.2 series and updated Linux only and labeled it 1.4.3 series, making the latest Linux update the Only change from 1.4.2 to 1.4.3.

Edit: then again my meds may be tweaking with my mind right now
[Samsung Epic 4G Touch] agat63:
Just to clarify all this test kernels.

1.4.2 has 2 versions

a). Update to Linux version 3.0.82. No frandom module

b). Linux version 3.0.75 (same as 1.3.0). With frandom module.

1.4.3

a). Update to Linux version 3.0.83. No fandom module.

b). Update to Linux version 3.0.83 with frandom module.

Since we weren't sure what causes the freezes and SOD updates or frandom I made 2 versions of 1.4.2 to try to narrow it down.

But then new update to Linux version came along. 3.0.83.

I made 2 versions of kernel with and without frandom in good hope that if there were problems with 3.0.82 update the new one might of fix that.

I know there are too many in testing now and it might create the confusion but I think this way we can figure out the root of the problem faster.

Hope this helps a bit.....
[Samsung Epic 4G Touch] cdss:
I just flashed 1.4.2 , will see how it performs ,on Project X 2.0 Rom.
[Samsung Epic 4G Touch] btoddweber:
FYI...still no lock ups
[Samsung Epic 4G Touch] blackcanopy:
That's exactly what I thought was going on. Thanks for clarifying.

I've been running 1.3.4F since it dropped along with both CrossBreeder 6.20.13 and then 6.23.13 v2 without any freeze/reboot that wasn't user error.
[Samsung Epic 4G Touch] remotehugger:
been freezing up almost every time my phone went to sleep on 1.4.3f - went back to 1.4.2f to see how that goes -

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] btoddweber:
Just to let ya know no lock ups or freezing on 1.42 jellyverse and comadose 1.4
[Samsung Epic 4G Touch] infirno77:
Been running 1.4.3F with the 6.23 crossbreeder release. No SOD's, or freezes so far. Been a few hours. Previous cb release is what I think may have been an issue. Froze up on gps nav 4 times in 2 hours. Since the change, it's been running sweet. Original gb27 odexed/nos' ed/cb/plus 3minit framework.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Based on reports, I went back to 1.42F and flashed the latest CB last night and so far no SODs and the performance is great.
[Samsung Epic 4G Touch] btvolta:
Same here. I flashed 1.42F yesterday morning along with CB 6.23, and haven't had any issues at all.
[Samsung Epic 4G Touch] cdss:
Where can I find CB?
[Samsung Epic 4G Touch] infirno77:
http://xdaforums.com/showthread.php?p=37062006
[Samsung Epic 4G Touch] jt_hatch:
Minor update -- I saw all of the above, but can now verify that with Garwynn's 0.5.0 kernel (w/ agat's recovery) not only does back up work but restore works also. :p

(Made nandroid, wiped dalvik, wiped cache, flashed jellyverse 3.0, (re)flashed gar's 0.5.0 in same session -> boot loop. Rebooted into recovery, restored nandroid -> all well, back in jellyverse 2. Still getting the hang of flashing zips in JB: it seems a wee bit more touchy than GB/ICS were...)
[Samsung Epic 4G Touch] dataman:
Thanks for the info..

What I am not clear about is that why not just continue the development on the Garwynn Recovery 0.5.0 and add the enhancement to that as a newer version.

so far the only difference I see between the 2 is that Agat 1.0 has over clock and under volt in it. Why re-invent the wheel? Garwynn and Agat work together pretty hard to get the garwynn v0.5.0 going bug-less and smooth and I know Garwynn was trying to retire from E4GT.

I am not complaining or anything just trying to understand why not the more efficient looking route was taken and why a new one.

P.S> Would you please add the MD5 for the files built-in to them?

Enjoy Vagas!
[Samsung Epic 4G Touch] jt_hatch:
I know the md5 isn't baked into the tar, but agat usually uses devhost, which gives you an MD5 on the download page for his files. The devhost md5 for this tar is fde6ac39d35456cfd20dc40e272b57ad.

You can use md5checker app on your phone and/or one of many md5 check apps (on win7 I use one named "MD5 & SHA-1 Checksum Utility 1.1" from http:://raylin.wordpress.com) on your computer to manually double-check the md5 before flashing.
[Samsung Epic 4G Touch] dataman:
Thank you. I know there is a way to bake the MD5 in the Tar. it would be nice to have it in there.. sure I am lazy lol

I always check MD5 but it is much easier when it is built in. It reduces the nag from people with issues with bad downloads.
[Samsung Epic 4G Touch] agat63:
Since there were some problems with GB27 kernel made by Garwynn I started same thing on my end in attempt to narrow down the problem. We weren't completely sure if the problems are in the kernel or ramdisk/recovery.

Garwynn worked on his end and I was working on my end. By the time we got it down to some recovery script this kernel was pretty much ready. I did upload my recovery for Garwynn to take one last shot on it and to try to fix the problem.

So I added UV/UC/OC support and few governors and schedulers and posted the kernel.

I'm not trying to compete with Garwynn and I said I'm retiring from E4GT for some time now but JB is different from ICS as ICS was different from GB. So it took some combined effort to iron everything down.

Hopefully this will explain why we have 2 kernels instead of one.
[Samsung Epic 4G Touch] svicenty:
Thanks for all your help
[Samsung Epic 4G Touch] agat63:
GB27 v1.1.0 is up and running.

OP updated and Links posted.

Now we have tar and zip formats.

My thanks to leaderbuilder and g-ding84 for zip template.

Recovery is updated to version 0.3.5.

Thanks to Garwynn everything is working now.

I did try back up and restore. (hence the delay).

and wipe/factory reset.

Phone is booting and working fine.

Enjoy.
[Samsung Epic 4G Touch] tt281gt:
Link seems broken for the tar file
[Samsung Epic 4G Touch] agat63:
Link has been fixed.

Was a typo in URL address.

Thanks for feed back.
[Samsung Epic 4G Touch] prguzman1978:
Hey where's my SmartassV2 governor at? I hope is not hiding from me.

An idea that is developed and put into action is more important than an idea that exists only as an idea...
[Samsung Epic 4G Touch] freakdonkey:
Flashing and testing

Sent from Astapor
[Samsung Epic 4G Touch] agat63:
If you want it that badly I'll add it tonight. ;)