yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] dataman:
right I read that so.. How do noob users who don't do coding fix this?

Would you please upload the fixed tweak file minus the lines that cause the issue and some instruction on how to fix it or maybe a zip file to flash?

Thank you!
[Samsung Epic 4G Touch] garwynn:
Well... 3.13a in testing. Found data partition size missing in fstab, comparing stock versus Agat's version.

Backup got to md5 checksum and rebooted. Unfortunately didn't save md5 so that backup is shot.

Data wipe.... no errors , got to Welcome screen and boot loops.

That sounds like progress but with some work to still do.
[Samsung Epic 4G Touch] helix4u:
To prepare for install of 0.3.0 so you can play with governors:

Easiest way to do get it done is remove any tweaks that you've previously installed. (Kobridge provides Stock_NoTweak.zip files to do this if you're using one of his tweaks).

Next if you want neat tweaks... Install Goddly's ComaDose1.4_CrossBreeder from http://xdaforums.com/showthread.php?t=2188416

If you just want to try 0.1.0 or 0.3.1, then no adjustments to tweaks are necessary.
[Samsung Epic 4G Touch] dataman:
ohhh, Thank you for clarifying that.

so the issue is the Kobridge Tweak Pack v4.34. I use the aggressive tweak. How is Goddly's ComaDose1.4_CrossBreeder compared?

perhaps this is the wrong place to discuss that...
[Samsung Epic 4G Touch] garwynn:
Out of curiosity I swapped out the ICS recovery build and dropped into JB ramdisk.

Backup completed but rebooted right after, data wipe did worse than before.

(Took the screen to all black after about 1 minute, no reboot.)

Back to the drawing board...
[Samsung Epic 4G Touch] helix4u:
The problem is in any JB kobridge tweakpack I believe, but I don't think Kobridge plans on supporting custom kernels with his tweakpack... so its a mod it yourself kind of deal.

Goddly uses kobridge's v4.2 tweak in his stuff along with other tweaks and has modded the problematic script for you. KO's 4.34 isn't too much different than 4.2. so you aren't missing out on too much. I haven't used Goddly's tweak pack quite yet, so I can't make a comparison.
[Samsung Epic 4G Touch] dataman:
Thanks

so I am running

Ko's Rom + CSC, Camera and System + TD's AIO minus Kobridge Tweak Pack v4.34 added Goddly's Comadose collection on GArwynn Kernel 3.0

things are running nice on pegasus.

Thanks guys we will see where we go from here...
[Samsung Epic 4G Touch] Goddly:
remember to please allow a full deplete charge cycle, before comparing battery stats, Im really quite happy with this tweak pack.. ;) I know it sounds weird, a dev talking about his work, but, 4 months ago i was just testing a script here, there, one at a time . wait a few days to get proper results, all previous setups were not improving much, until i put together ComaDose V.1 my battery life became "gotta expect it, its jelly bean" to "wow, is this still jelly bean"? ... plus i love patting myself on the pack... :)
[Samsung Epic 4G Touch] kobridge:
If my time allows me to work on the tweak after my current project, I'll repost the modified Kobridge Tweak pack v5.0 with Ondemand governor based. Alo planning to release couple of more tweaks based on other governors.

Don't wait too much, I don't know when it's going to happen tho.
[Samsung Epic 4G Touch] CyberpodS2:
Looks like 4G works with the 3.7 kernel, and gps rocks too!
[Samsung Epic 4G Touch] garwynn:
Traylunch and I have tried 0.1.0 and for backups and restores seems good.

Data wipe still is no good though.

Making yet another test build by clearing and recloning Agat's ramdisk.

Maybe something was wrong in there so I'll pull it again to make sure.

If not we may have to back to scratch and try this all over again.

Update:

I can backup in test c but still reboots.

Feels like we're making progress but not good enough.

Wish I knew what was causing the reboots.
[Samsung Epic 4G Touch] PanchoPlanet:
The new jb update from Samsung gives the option in managing apps, when you look@d/l apps you see the option to "move to sd card".

Pp. :beer::thumbup::)

Sent from a bean shooting Epic Touch ......in your eye ....phone.
[Samsung Epic 4G Touch] JSnively:
Has. Anyone tried a backup full wipe and restore?
[Samsung Epic 4G Touch] svicenty:
Installed my paid apps from play store everything went well thanks GARWYNN
[Samsung Epic 4G Touch] robrooter:
Been keeping phone pretty stock.

Data wipe with restore

data and cache wipe for Any and ALL additional zips flashed there after.

Reflassh kernel once again with another data cache wipe..

REBOOT recovery!

Than restart rom from recovery :thumbup:

My friend you are good to go!

Have found that my keyboard is freezing then completely reloading is occurring.

Is there a service that runs this perhaps that I may run on frozen?

Other than that it has been a nice kernel. Seems faster.

:beer::beer::beer:

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] jdsingle76:
I did during testing for agat with GC01. Worked like a charm:)
[Samsung Epic 4G Touch] garwynn:
How about rwilco's site?
[Samsung Epic 4G Touch] garwynn:
Yes, it's safe. At some point i'll summarize the whole ordeal in a single post.
[Samsung Epic 4G Touch] aburns7487:
this GB 27 Agat repack kernel Sounds great! with the GB27 Jelly verse 2.0 to would take away the old Agat Recovery. I'm glad to Kernel will be latest for Latest Rom. Can't wait to download and put On my girlfriends phone.
[Samsung Epic 4G Touch] Sloth:
Thank You for the reply sir :D
[Samsung Epic 4G Touch] WhiteZero:
That'll work as soon as it gets upped. :D
[Samsung Epic 4G Touch] cerj:
garwynn, what can I say but, Thank You. All paid apps are showing, and everything is working. Will make a nandroid and report back. Looking real good

---------- Post added at 09:42 AM ---------- Previous post was at 09:31 AM ----------

Thank you for everything, its Devs like you, that make this the place to be. Good luck in all your endeavors.
[Samsung Epic 4G Touch] robrooter:
Mirror up...

"SXTP_Agat_GB27-v0.1.0-1.tar" - http://www.4shared.com/file/pIqDTjvN/SXTP_Agat_GB27-v010-1.html

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] WhiteZero:
Thanks!

And with that, I'm wondering if garwynn would post hashes of the original... because I'm paranoid like that. lol
[Samsung Epic 4G Touch] Stryke_the_Orc:
Thank you for all your hard work with the E4GT Gar. It's sad to see you go, but as this device has reached EOL and will soon probably be a legacy forum, I understand.

On a more on topic related note, I've flashed, recovered, backed up, recovered, factory reset, etc... without issue. Not sure if there's anything else you'd like tested, if so just say the word:D
[Samsung Epic 4G Touch] robrooter:
Sorry bout the site. I use it cause it free. File was downloaded fresh for you :thumbup:

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] garwynn:
Didn't generate for the initial builds as was in a hurry.
[Samsung Epic 4G Touch] MoHoGalore:
Noticing the name change on the 4Shared Mirror, not sure it's going to match.. (It has the added -1 at the end of the name..)

But for comparison for you WhiteZero - DB9E1EB713EC7A1A9D7FA960E8F90C84 SXTP_Agat_GB27-v0.1.0.tar

:Edit: I just checked against the 4Shared download. MD5 matches.
[Samsung Epic 4G Touch] robrooter:
It is a link to file. I klick it and file shows up. The "-1" is his download number. I copied him a fresh file. That was the name.

E4GT Rom-a-holic. Running anything that looks cool at the time ;)

"This is the Droid I have been looking for!"
[Samsung Epic 4G Touch] WhiteZero:
Thanks!

Yeah, file names and metadata don't factor into hashes, only file contents.
[Samsung Epic 4G Touch] MoHoGalore:
All is well. Thanks for helping out the request by WhiteZero. I'm sure, once testing is done, that it'll be housed in the Repo so the issue won't remain but helping others is good. (As long as Garwynn is ok with a mirror.)

Welcome sir. Always good to double check.
[Samsung Epic 4G Touch] cerj:
Just wanna thank you garwynn, for all you are doing to leave us with a working kernel/recovery. Really speaks of character
[Samsung Epic 4G Touch] jdsingle76:
I'll second that garwynn. You and Agat have done so much for this phone, and I know you've racked your brain since source dropped trying to crank out stuff. Great job my friend. Hat's off...:beer: on me!
[Samsung Epic 4G Touch] emottau:
Plus 1! And as far as leaving goes, take me with you! !
[Samsung Epic 4G Touch] djjosh:
Whats the md5 for 0.3.0 ? Please
[Samsung Epic 4G Touch] helix4u:
I get the following:

SXTP_Agat_GB27-v0.3.0.tar 64A5C063CC11E1436FD903CA6008B247

SXTP_Agat_GB27-v0.3.0.zip 06751C125D3CCB919E54A53DCCFF6F28
[Samsung Epic 4G Touch] helix4u:
Hey man... I was trying to modify the 4.34A tweaks to mirror what you did in comadose 1.4 and I realized that in the 41tweaks_kobridge script that has been giving us troubles with the 0.3.0 kernel, you're missing a new line before the command that causes the reboots (see attached). Essentially, without the new line it breaks the command and it never ends up issuing sysctl -w kernel.hung_task_timeout_secs=30... If you put a new line in before it to fix the formatting issue, it starts the rebooting issue again. :( I'm betting that no matter what we take out, if sysctl -w kernel.hung_task_timeout_secs=30 is still there, we'll still have the rebooting issue.
[Samsung Epic 4G Touch] Goddly:
testing......

confirmed.....

Dumping the entire script ..

simple as missing the enter button.. lol like i said, i was just trying to help out with the reboots, im done with it, Thanx for the find! made my day........ lol
[Samsung Epic 4G Touch] helix4u:
Yeah, script works fine without the kernel task timeout line... stock defaults to 0 instead of 30, which basically means "Timeout? Who cares...". So you could put the other lines you took out back in and remove the kernel task timeout line and be none the worse than running without the script. Up to you dude... I think hotplug just isn't playing well with task timeouts all together.

The test would be: No tweaks > Add a one line tweak that only does sysctl -w kernel.hung_task_timeout_secs=30 or just run the command in a terminal emulator or adb as su and see if reboots occur.
[Samsung Epic 4G Touch] duce415:
I installed 3.0 ladt night and I'm running it without any tweaks. Using the peq governor so going to run it for a couple of days and see if I notice and difference with or w/o the tweaks (kobridge or goddly) . Will keep yall posted.
[Samsung Epic 4G Touch] garwynn:
Morning everyone!

I'm going to try a different approach today.... and just internal testing - likely no new posted builds.

Going to take the stock ramdisk and swap out recovery only. No init.d support, nothing else. Let's see if that gets a functional recovery. To me this is the highest priority because without a working recovery (and GB27 repack does it but you have to flash stock back right after) most people are not going to use it.

Updates after I test it out.
[Samsung Epic 4G Touch] prguzman1978:
It will be nice to have a permanent recovery without it being repacked with the kernel, thanx for ya work homey!!!
[Samsung Epic 4G Touch] crawrj:
Unfortunately it has to be part of the kernel. What he is going to do is try adding the recovery to the stock kernel without making any other changes to see how it performs. If everything is great he can release that one and then start adding things to it until he gets to the completed fully tweaked kernel.
[Samsung Epic 4G Touch] prguzman1978:
I know Agat told me that the GS3 community doesn't have to deal with repacked kernels, the recovery stands alone.

Three things cannot be long hidden: the sun, the moon, and the truth...
[Samsung Epic 4G Touch] crawrj:
Yeah the S3 has a dedicated Recovery like the OG Epic had. I always hated that the S2 went to the recovery being built into the kernel.
[Samsung Epic 4G Touch] prguzman1978:
I remember when I had my evo shift I was experimenting on a series of kernels only through one recovery...

Three things cannot be long hidden: the sun, the moon, and the truth...
[Samsung Epic 4G Touch] garwynn:
Well... today's testing was informative.

I'm documenting here mainly for Agat and other dev input.

1) Backup process is okay - recovery looks okay too.

Noticeably slower than Agat's tRec 0.2.2 though.

2) Even if #1 is true (which proved in 0.1.0) you're on a timer with everything after 0.1.0.

I haven't narrowed down what it is but I think something's causing a kernel panic/reboot.

If folks have time, run this test.

Download any version past 0.2.0 and boot to recovery.

Don't do anything and wait for it to reboot. Time it and note it here.

I want to see if it's always at the same time or not. (Didn't time it yet)

3) Compared to ICS kernel is big - like near 8 MB big.

New recovery is almost 900KB and may be the majority of the difference.

Could this be causing some of the issues?

I'm almost tempted to make sure Agat's using my repo when building his recovery.

It just seems too big and too slow, even with the kernel.

4) Will ICS ramdisk work? Not as it was.

I'm curious if 0.2.2 recovery could do the trick though by dropping into JB ramdisk.

In ICS it couldn't back up system or utilize system properly.

That's the long story shortened.

0.1.0 still seems the best bet for a daily.
[Samsung Epic 4G Touch] blackcanopy:
Could it be that Agat's JB recovery is being based off of CM10 JB source?

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] jdsingle76:
Garywnn, not sure exactly what all you wanted, so I ran a few different tests. Setup: GC01 deodexed, flashed GC01 0.3.0 using Mobile Odin. With clear dalvik box checked, 1min51sec to reboot. Unchecked, 20sec to reboot. Rebooted to recovery, hit "reboot system now" took 27sec. Let me know if you need anything else! Thanks for your work man :thumbup:
[Samsung Epic 4G Touch] garwynn:
Unless he recompiled, yes. It's why I had issues with GN2 attempt.
[Samsung Epic 4G Touch] garwynn:
Actually, what I'm looking for is:

1) Boot to recovery.

2) As soon as you see the menu appear, start timing. Don't do anything - it will reboot on its own.

3) Note the time it rebooted and post here.

For even more testing, Step 2 can be doing other operations - backing up, restoring, etc.

We just want to track how long you can stay in recovery before it reboots on its own.

(And more importantly, is there a pattern that may help indicate what's causing it?)
[Samsung Epic 4G Touch] jdsingle76:
Ok, I can do that. Will let you know!
[Samsung Epic 4G Touch] Sherbon26:
Im running the GB27_v0.3.13 and also have comadose 1.4 with cross breeder and went over 5 minutes without it rebooting.....got impatient and battery is very low will recharge and see how long it will stay up.
[Samsung Epic 4G Touch] CyberpodS2:
Ok using 0.3.7 and modified comatose on WOR it restarted at 3:47 two times in a row. Only problem of I was not able to reboot after the exercise. Tried 0.1.0 & 0.2.0 with no luck either. Tried deleting cache, etc but it would not get past the Samsung screen. Waited like 5 minutes several times. Since I'm away for a week I did not want to flash the stock kernel for fear of losing the recovery. I restored PacInBlack for now and will join the party next week. I'm looking forward to seeing what other folks get in their tests. I am wondering why after letting it reboot itself in recovery it boned up normal booting. Good hunting guys!
[Samsung Epic 4G Touch] Sherbon26:
That is crazy I have never seen that happen before...thankfully your nandroid worked I got a md5 does not match when I tried mine on the 0.3.13 kernal

Sent from my SPH-D710 using Xparent Red Tapatalk 2
[Samsung Epic 4G Touch] MoHoGalore:
No spaces in the name right?
[Samsung Epic 4G Touch] helix4u:
4 min on the dot from recovery screen turning on to reboot.

lol... I can maths today...

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

K, don't laugh, but you're also having the sysctl -w kernel.hung_task_timeout_secs issue. I just booted into adb shell while in recovery, issued the command sysctl -w kernel.hung_task_timeout_secs=0, and now instead of rebooting after 4 min, its been about 15min... no reboots.

Agat runs "write /proc/sys/kernel/hung_task_timeout_secs 0" in init.rc.. but its just not being honored or something...
[Samsung Epic 4G Touch] garwynn:
Hey guys.. going to have to keep plugging away at this solo for a little longer. Our man Agat is apparently out for a while. More if I get an okay to post.
[Samsung Epic 4G Touch] garwynn:
Huh. let me take a peek. Might need to add to recovery.rc.

But now it begs the question - what's hanging? Ignoring it still doesn't tell us what's causing it.

At some point we still need to find that.

Update: Think we're on the right track.

Going to add that part of init.rc to recovery.rc.
[Samsung Epic 4G Touch] helix4u:
Agreed. I'm leaning toward something to to with hotplug not playing nice...
[Samsung Epic 4G Touch] garwynn:
I'll remove hotplug from cpufreq module outright. I'm not including it in the defconfig for what I'm testing because it was removed by the make oldconfig command. I do see another option for hotplug in there - maybe it's built in now.

But before that... making test build h with edited recovery.rc.

Edit 2: While waiting, found this in updated defconfig:

#
# Support dynamic CPU Hotplug
#
CONFIG_EXYNOS_PM_HOTPLUG=y
# CONFIG_STAND_ALONE_POLICY is not set
CONFIG_LEGACY_HOTPLUG_POLICY=y
# CONFIG_WITH_DVFS_POLICY is not set
# CONFIG_DVFS_NR_RUNNING_POLICY is not set
# CONFIG_NR_RUNNING_POLICY is not set

Let's see if search is our friend today...

Edit 2: Another line that looks wrong:

CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"

I'll push out Test h and remove both in a new test I.

Let's see how both of those do.
[Samsung Epic 4G Touch] helix4u:
I'm trying out a backup... to see if it completes... Oh, FYI, I'm using 0.3.0 for this.

Edit:...Backup completed. yay!

Maybe its an issue with how hotplug is being handled in https://github.com/garwynn/D710SPR_GB27_Kernel/blob/master/kernel/watchdog.c ...purely guessing at this point.

Edit2: Now trying restore...

Found a thread on your uevent helper... http://xdaforums.com/showthread.php?t=1138941 Looks like they recommend disabling it.

Edit3: Restore completed... booted into rom, no issue to report. :D
[Samsung Epic 4G Touch] garwynn:
Tests 0.3.13h through j now posted on OP on SXTP Developers along with what they test.

Everyone please start putting these through the wringer...
[Samsung Epic 4G Touch] Sherbon26:
Correct no spaces...left it just the way it was written by the nandroid backup

Sent from my SPH-D710 using Xparent Red Tapatalk 2
[Samsung Epic 4G Touch] garwynn:
H test results -

Backup/Restore - OK.

Data Wipe - LONG delay getting past 4G screen. Quickly skip through welcome steps, about to put in name and it soft reboots. But progress!
[Samsung Epic 4G Touch] garwynn:
I test results same as h.

Key to cause reboot after data wipe is apparently keyboard display.

This time though it went to a black screen.

Now to try J.
[Samsung Epic 4G Touch] helix4u:
H-results:

Backup/Restore - OK

Data wipe gives me boot animation loops.

"E:unknown volume or path [/sd-ext] error" on wipe dalvik cache. <-(not a new issue)

Garwynn, did 0.1.0 have data wipe issues as well? or it good?

my backups/restores take a million years... probably because I use the phone. lol... I'm thinking I'll make a no-data, stock, out of the box nandroid to backup/restore from so I'm not moving all that data all of the time.

Edit: I get boot animation loops when doing a data wipe with agat's repack, so I probably have another issue entirely. I'll have to track it down before I can give any reliable feedback on these.

Edit2: HA! Had some fun there for a min... Loaded 'I' and 'J' and my sdcard didn't want to mount... which meant no mobile odin sdcard access, no recovery sdcard access... Thank god for good ol oneclicks.

Note: looking at cat /proc/kmsg in I and J, I didn't see the regular cpu1 off, cpu1 on jibber-jabber that hotplug usually outputs there.. so I believe either one of those (I or J) DOES pretty much turn off hotplug, but breaks sdcard access for me.
[Samsung Epic 4G Touch] moparfreak426:
I'm so thankful for such an awesome delving community

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Ain't that the truth! :thumbup:

Cheers!
[Samsung Epic 4G Touch] garwynn:
Ill plug away at this a little more today and test data wipe from 0.1.0.
[Samsung Epic 4G Touch] moparfreak426:
Eep eep woop woop

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] garwynn:
Cleaned up OP and put test build 0.3.14 out.

Verified I can see both external and internal memory from recovery.

Data wipe still NG, haven't tested ROM side out yet.

Backups/Restores seem to be a little faster but may be placebo effect.

Hm. This is odd.

Flashed 0.1.0, wiped data, bootloops. OK, so it's never worked.

Flashed 0.3.14, booted straight to recovery - can't mount /sdcard. Now THAT's odd.

Booted back to Odin mode, reflashed, booted straight to recovery again - okay now.
[Samsung Epic 4G Touch] leaderbuilder:
Will certainly give this a go if I can get a few free minutes.

Thanks garwynn and all the others for the superb work and support!
[Samsung Epic 4G Touch] Goddly:
Just wanna remind you guys of a bug with 3.0, when phone is powered off, then plugged in, it powers itself on..... lol. Just reporting...
[Samsung Epic 4G Touch] garwynn:
Just started this test with 0.3.14 and so far has stayed at battery screen.

Update:

Just booted into ROM. Huh,odd.
[Samsung Epic 4G Touch] Goddly:
Yea, thats what i said.. lol
[Samsung Epic 4G Touch] helix4u:
Yeah, 0.3.13h has been the most kind to me so far.
[Samsung Epic 4G Touch] leaderbuilder:
Lost external SD in recovery and in OS with 3.14. :/
[Samsung Epic 4G Touch] tdunham:
Asked this a while ago but never really got an answer.

Is the preload partition getting backed up yet?
[Samsung Epic 4G Touch] leaderbuilder:
It didn't for me last time I did a full wipe (X2) and restore.

I've had to flash the base ROM (Stock GB27.tar) via mobile Odin, flash the original AGAT_GB27_repack.tar (again Mobile Odin) then boot to recovery and restore. Doing that brought me back to my daily driver - Stock, GB27.All-In-One.Mod.Rev3.Odex and all my settings, apps and files.

Without flashing whatever base ROM (Stock, TBSIV, KO's etc) I would not have a working system - no preload partition.

But on the later builds - 2.0 and all the 3.x (except 3.1 - which is what I'm using now as DD and what I've used to make nandroids) I couldn't even get a full nandroid without errors.

Been really busy all week but I'll see if I can do some more ROM 'switching' - CM/AOSP and back. Doing those I have to use EL26 do full wipes etc. And then come back for my DD.

But this is just my experience.
[Samsung Epic 4G Touch] helix4u:
0.3.13h will do full nandroids without error and includes the new govs. I don't believe there are any changes to recovery in it... not sure. Seems to perform pretty much the same as 0.1.0 and 0.3.1 when it comes to recovery.
[Samsung Epic 4G Touch] tdunham:
Just checking. At some point it would be nice if we could get a FULL backup like we're used to. A working kernel takes first priority of course. ;)

The preload is just as important as the system partition. The system partition is so full I've started moved apps and even framework files back over to the preload partition just to make room in the system partition for larger mods.

(For anyone that doesn't know, the system partition contains far more than just apps, it contains all the binary, library, sound and framework files as well... among other things).
[Samsung Epic 4G Touch] kobridge:
This is the main reason that I bricked my phone last time. I hated this small system partition and jealous other G2 phone's partition size. So, I tried to repartition it. Guess what? We need to extremely careful about this!