yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] HulkSmashBurgers:
Sorry, I'm new to this and the file names confuse me. SXTP_Agat_VMUBFL26-v0.2.0 does not contain the FL26 kernel and/or modem? I don't get why FL26 is in the file name, since there is an iCS modem called FL26.

I can flash SXTP_Agat_VMUBFL26-v0.2.0.tar with Mobile Odin and I will have the same stock GB28 modem and kernel I do now, but with Agat's recovery?
[Samsung Epic 4G Touch] jdsingle76:
No, that's FL26. Is the GB28 not there? Edit: looks like GB28 is not there anymore. my apologies. The GB27 will change your kernel but leave modem, which is fine since if your phone is VM it will work fine. I used GB27 for awhile with boost and it's a great kernel+ recovery.

---------- Post added at 07:36 AM ---------- Previous post was at 07:26 AM ----------

Here's Agat's GB27 repack. Great daily driver.

http://xdaforums.com/showthread.php?t=2193849
[Samsung Epic 4G Touch] garwynn:
Version 0.2.0 is up. Fstab is fine since emmc and SD card are visible in recovery. Tested an alternate but that broke so went back to what works. Must be an issue in the USB mount process. I'll mention it to Agat.
[Samsung Epic 4G Touch] gharlane00:
Downloading now Thanks!
[Samsung Epic 4G Touch] rdavis429:
Garwynn, you rock :beer:

Blast through the Jellyverse
[Samsung Epic 4G Touch] dasesq:
Installed zip of 2.0 with 1.0 version recovery and all seems well (except the phone still tells me in about status that I'm "custom" :)

Edit: ok how to change governor extweaks won't

Oh and running sgs4 1.1. No boot loops
[Samsung Epic 4G Touch] dataman:
v0.2 was bad news for me

my phone would not load or would restart randomly every few min..

back to v0.1
[Samsung Epic 4G Touch] dasesq:
Still all seems fine here. wonder if it's the rom or maybe our modifications thereto?
[Samsung Epic 4G Touch] Shadow_God:
Did you flash or odin?

MISTAKES are proof you are TRYING....sent from the Jellyverse...far, far away.....
[Samsung Epic 4G Touch] cerj:
use SetCPU. its not set up for extweaks
[Samsung Epic 4G Touch] gradford11:
Bootloops and reboots for me with v0.2. I tried to flash using v0.1, no go, then I tried El26+CWM same results.

Edit: I forgot to test Odin. But I just did and same, it'll bootloop then load past boot then reboot.
[Samsung Epic 4G Touch] cerj:
I just got Shinja'd
[Samsung Epic 4G Touch] dataman:
Mobile odin...

so everyone else is doing fine?

what is the improvment in v0.2?
[Samsung Epic 4G Touch] cerj:
You can change governors, that garwynn added in
[Samsung Epic 4G Touch] dataman:
I will flash it with the zip see maybe the odin version is the issue
[Samsung Epic 4G Touch] rdavis429:
It's a no go for me with .2 going back to v1. Got bootloops and random reboots, going back to v1 for the time being. Thanks for all your hard work Garwynn and Agat!!
[Samsung Epic 4G Touch] graydiggy:
Tried flashing 2.0 with mobile odin. It wouldn't stick. Flashed the zip with 1.0 and it stuck.
[Samsung Epic 4G Touch] dataman:
I guess we are seeing a pattern

people who use odin .tar have issues...

check the md5 for us when you can
[Samsung Epic 4G Touch] btoddweber:
Flashed v2 and bootlooped in rec and mobile odin..had to full restore then reflash jv
[Samsung Epic 4G Touch] garwynn:
Let me fire up Virgin test now then will flash Sprint OC and 0.2.0 kernel
[Samsung Epic 4G Touch] gradford11:
Tar and Zip both failed for me.
[Samsung Epic 4G Touch] garwynn:
GB27 0.2.0 - which should match others - works fine on clean phone. I'll check Sprint md5 and if matches flash and test.
[Samsung Epic 4G Touch] dataman:
Thanks Garwynn...

well there is an issue somewhere too many people have issues.
[Samsung Epic 4G Touch] jaxon01:
I flashed the zip of v0.2.0 from v0.1.0 and had no problems. All I did was wipe cache and dalvic cache before flashing.

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] garwynn:
0.2.0 update:

MD5 matched, flashed GB27 nodata over clean GB28.

Then flashed GB27 v0.2.0

Stable and no issues yet.

Those having issues - logcats will help track down the issue. Any that you can send are appreciated.

Tar md5: 5ed180f6c1ef63fde09a21a159b0f60e
[Samsung Epic 4G Touch] im0rtalz:
Maybe add md5 right into the .tar file

$ tar -H ustar -c recovery.bin > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5

That's what I had used when making the el29directboot

the last part being what ever name you choose instead of recovery.tar.md5
[Samsung Epic 4G Touch] garwynn:
Normally do.. just ran out of time today. Will add to scripts tomorrow.
[Samsung Epic 4G Touch] dataman:
cleared cache and dalvik and still reboots i give up for now

both odin and recovery
[Samsung Epic 4G Touch] optimummind:
Flashed over v0.1 using Mobile Odin Pro and everything is fine. :D I'm on the original GB27 sextape leak which was installed via Mobile Odin Pro.
[Samsung Epic 4G Touch] boXerrumble:
Just flashed the 0.2.0 zip over 0.1.0 in recovery, and everything works. Not really sure why some have no issues, and others have issues. Bad flash or download?
[Samsung Epic 4G Touch] btoddweber:
Flashed v2 over v1...could boot to recovery but just looped at home screen. Has to dirty flash rom twice to boot out. Used zip and mobile odin tar..no luck:banghead::banghead::banghead:
[Samsung Epic 4G Touch] jaxon01:
I wonder if the problems are only with certain roms?

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] Shadow_God:
Did you wipe cache and davik? or just cache?

Thunder Buddies 4 Life!!!!!!!
[Samsung Epic 4G Touch] JCred:
Just tried to flash the .2.0 .tar over .1.0 in mobile Odin pro and got "partition not found in file" error. I'm assuming bad download and will try again later. Version 1 has been good, so far.
[Samsung Epic 4G Touch] abodamer:
I used mobile odin lite to flash the 0.2 tar over the GB27 stock rooted. No issues here.
[Samsung Epic 4G Touch] btoddweber:
Both
[Samsung Epic 4G Touch] CyberpodS2:
I had the same thing with rebooting on 0.2.0 as the other guy... Tried both the tar and zip. I am running WOR. I gotta hit the sack tonight so just went back to 0.1.0 for now. Sorry I am not much help, I'll try to dig out some more info after work tomorrow if I can.
[Samsung Epic 4G Touch] blackcanopy:
I was running Jellyverse with comadose1.3 tweaks and getting bootloops and random reboots after flashing the 0.2 kennel.

I deleted the init.d folder (comadose1.3 tweaks) and flashed the 0.2 kernel and all is well. I'm thinking there may be something in that tweak Pack causing issues with the kernel. So if your having issues with this kernel, try removing some tweaks before giving up completely and thinking the kernel is bad.

Thank you garwynn for seeing the source built kernel thru. And the extra governors.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] jdsingle76:
I hate to keep piling on, but I just flashed .2 with mobile Odin with wipe dalvik checked, over 0.1, running JV, no issues, smooth. Thanks garwynn and Agat! Awesome as always :)
[Samsung Epic 4G Touch] btoddweber:
So how would I del comadose tweaks? If thats the prob them how come v1 works? Could that really be it?
[Samsung Epic 4G Touch] g_ding84:
Hmm I think you maybe on to something with the tweak package. I'm having issues with both of my ROMs. I haven't released TDAR yet due to the issues with TBSGS4. I'm going to be doing some testing and see if removing them makes a difference.
[Samsung Epic 4G Touch] blackcanopy:
Remember version 2 introduces new governors (maybe settings too?) to remove those tweaks, simply delete the init.d folder.

Has anybody ran into reboot issues using Kobridge tweaks? I tried flashing the Kobridge Jellyverse aggressive tweaks and ended up with issues again. I flashes the Kobridge tweak remover and everything is fine again. Could the possible be conflict in the zipalign script used in both tweak sets?

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] gradford11:
Testing this theory now... I'll report back.
[Samsung Epic 4G Touch] Stryke_the_Orc:
Kobridge tweaks are in comadose, so I'm not sure you'd see any change. It could be those tweaks or exit's thats causing the conflict only way to know for sure is to try them one at a time. However, I think I now understand why I've had no problems while various random users have.

If these tweaks are indeed causing issues we need to find out who's running what.

How many are running Ko's vs how many running exit's vs how many running comadose. What versions of the tweaks are causing issues, etc...

Process of elimination:thumbup::beer:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] btoddweber:
They say exit_only init.d? Is that the ones to del?
[Samsung Epic 4G Touch] gradford11:
I can say right from the gate, it was the tweak package. I deleted the init.d folder and sure enough,.. Wala
[Samsung Epic 4G Touch] btoddweber:
Im using jv 2 with comadose 1.3..would I del the exit_onlt init.d folder?
[Samsung Epic 4G Touch] dataman:
I am running the Kobridge ROM and all the tweaks plus AIO from TD

and I sure have the issue with v0.2

so he will be adjusting their tweak here Ko/TD or Agat/Garwyn?
[Samsung Epic 4G Touch] boXerrumble:
Been running Exit_Only's 0.3.2r1 and Cross Breeder with the 0.1.0 and 0.2.0. No issues so far with me with reboots and bootloops.

Maybe theres a tweak in the Comadose package that messes with one of the Governors in 0.2.0?
[Samsung Epic 4G Touch] gradford11:
Twenty minutes later and still, all is well. I couldn't get two minutes without reboots before. Thanks blackcanopy and g_ding84 for your ah ha moment. :beer:
[Samsung Epic 4G Touch] blackcanopy:
I'm using TD's AIO with 0.2 just fine. The only thing giving ME issue is trying to use KO or goodly tweak packs.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] fredrick1213:
Yea it was definitely a problem with the ComaDose tweaks. I deleted them and all is well
[Samsung Epic 4G Touch] btoddweber:
How????
[Samsung Epic 4G Touch] blackcanopy:
If you are using comadose, use root Explorer or equivalent to navigate to system /etc and delete the init.d folder.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] btoddweber:
This is what i see
[Samsung Epic 4G Touch] astolenheart:
Guess it was a tweak issue guess ill go back to pimp my rom until new tweaks comes out

Send from a mircowave
[Samsung Epic 4G Touch] mradlauer:
I had reboot issues as well. Removed init.d and am back to normal.

Had Ko's tweak, his zip align and something else in there.. Dont remember.
[Samsung Epic 4G Touch] leaderbuilder:
So it looks like Kobridge's tweaks were my issue too! Deleted /system/etc/init.d and it booted, and is working! Thanks blackcanopy, g_ding84 and the others for getting the 'ah ha' and thinking about that! Now back to seeing what I can break next!

Once again this forum shows why it kicks A$$.
[Samsung Epic 4G Touch] Mattix724:
I noticed battery life on version 1 with Jellyverse 1.0 and Comodose 1.3 is a whole lot better than it was on the stock kernel.

15 minutes of screen on time so far and still 100%
[Samsung Epic 4G Touch] leaderbuilder:
So what are folks using to tweak this kernel with here?

ExTweaks doesn't work with this kernel. ROM Toolbox (Pro) won't let me raise or lower the CPU speed and neither will Pimp my ROM.
[Samsung Epic 4G Touch] garwynn:
Glad we figured out what it was! Was seriously considering a rollback of some changes.

Those wanting to tweak... we have 30 incremental updates (at least) to still apply to make it current. I'm going to hold off on other stuff until that is done. Hopefully I can finish it in 2 stages. Also would not make too many changes to tweaks until then to avoid changing again.
[Samsung Epic 4G Touch] leaderbuilder:
Thanks G that rocks!
[Samsung Epic 4G Touch] CyberpodS2:
Yah, WOR uses comadose so that was my problem. All is well now... Thanks everyone for pulling an all nighter. LOL
[Samsung Epic 4G Touch] garwynn:
0.3.0 is out and Linux is now current at 3.0.71
[Samsung Epic 4G Touch] blackcanopy:
Update on using comadose tweaks..

I removed the 19_gpurender_2d and 41_tweaks_kobridge scripts found in unit.d folder and everything else in comadose1.3 is playing nicely with both kennels (0.2.0 / 0.3.0.)

The 41_tweaks_Kobridge script is present in both kobridge and comadose tweaks, so I'm guessing it's something in that script conflicting for now.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] dschachm:
Flashing v3 right now, thanks for your fast work. Was wondering, is there a way to post a change log in the OP? thanks
[Samsung Epic 4G Touch] fredrick1213:
You're a machine! :eek: Thanks for your hard work and dedication
[Samsung Epic 4G Touch] astolenheart:
Setcpu?

Send from a mircowave
[Samsung Epic 4G Touch] CyberpodS2:
That's what i am using right now
[Samsung Epic 4G Touch] btoddweber:
Finally got v3 to stick..looked and where are the gov settings.
[Samsung Epic 4G Touch] kobridge:
Definitely it appaer that this kernel v2 and v3 do not supporting the tweaks based on stock rom.

It's not the tweak issue and I believe every Kernel changes should be based on stock options.

Adding the governors should be based on stock and only add the extended governors and features.

For now, I'm going back to initial version which only has CWM recovery option.
[Samsung Epic 4G Touch] DarkEye45:
Just flashed the 0.3.0 zip over 0.1.0 in recovery, I did a wipe cache and davik cache before flash.

Now I'm getting a reboot during app setup. In a reboot loop.

Flashed back to 0.1.0 in recovery and now back to normal and working.

I'm using MIJJz JB GOODNESS JB 4.1.2 FK23 v1.0.3 (Updated 12/21/2012) ROM and have been on it for months. Have SetCPU running.
[Samsung Epic 4G Touch] dataman:
Clean all Cache before flashing files...

The only issue I had with v0.1 was that it would not morph some files I was flashing till I cleared dalvik cache.

Is there any fix for that?
[Samsung Epic 4G Touch] DarkEye45:
How do you delete the init.d folder if the phone is in a reboot loop?

Can the folder be deleted from within recovery?

I had to flash back to 0.1.0 to get my phone back to stable.
[Samsung Epic 4G Touch] blackcanopy:
You could flash the old kernel and boot into its recovery... Boot up and remove tasks and reflash new kernel

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] garwynn:
I'm going to make a 0.3.1 in a little bit that uses the default defconfig again.

It means all that should be there is stock + linux updates.

Let's see how that works out for kobridge and others.
[Samsung Epic 4G Touch] dataman:
THANK YOU!

any idea if the problem I mentioned will be fixed too? do you know what causes it?
[Samsung Epic 4G Touch] garwynn:
No... and to be honest it's the first time I saw that.

It's why I normally don't touch anything until I patch Linux first.

We'll know in a little bit when 0.3.1 is posted but may have gotten to cocky by trying to add that early.

Building now, I'll post tar as soon as it's up.

If anyone needs the ZIP say so and I can make it.
[Samsung Epic 4G Touch] dataman:
I had an issue flashing TD's patch and he mentioned that he has seen the issue with your v1 recovery that it does not morph till you clean all the caches.

so I was flashing the file, it would say flashing complete but it never did run the whole file.

I use Kobridges rom and tweaks and TD's AIO + call recorder. I will test the 3.1 and let you know.

it would be nice to have the zip unless it is too much trouble.

md5 built in with a cherry on top? lol
[Samsung Epic 4G Touch] garwynn:
0.3.1 is uploaded. Tar MD5 is 2cfd81a369b233fc24f96bc98750e4d4

Oddly with these I tried adding .tar.md5s to RainMotorsports but can't find on the web side.

Maybe too many periods.... :)

Zip in a few.

*Edit*

Zip up. MD5 - 6dd20e020f9566d7479b59d2033f9fdd
[Samsung Epic 4G Touch] PanchoPlanet:
Tried flashing using MO pro v1.0 over kobs deodexed w/ td AIO mod, wiped cashe/dalvik, did not remove init.d folder > boot loop.

Booted into agat recovery cleared cache/dalvik again still ng.

Back to agat recovery tried flashing backup from previous el29 safe recovery still ng.

Will try again. This time removing init.d folder.

Pp.:p
[Samsung Epic 4G Touch] im0rtalz:
that might not be the recovery fault since when we flash el26cwm to install the mod/zip, in the process of flashing the stock kernel, that zip if it's kobridge stock kernel zip it's scripted to clear cache during the install

just pointing that probably your previous method of morphing, the cache was cleared for you when you reflashed the stock kernel
[Samsung Epic 4G Touch] cerj:
Flashed 0.3.1 with Mobile Odin, Booted up with no probs. I did not check clear Cache's in Mob Odin, did boot into recovery after I flashed and wiped both without issue. Thank you garwynn
[Samsung Epic 4G Touch] garwynn:
For reference:

This is the difference between 0.3.0 and 0.3.1 - defconfig only.

(Differences highlighted in bold)

0.3.0:

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ADAPTIVE is not set
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_PEGASUSQ is not set[/B]
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_SMARTASS2 is not set[/B]
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_HOTPLUG is not set[/B]
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_LAGFREE is not set[/B]
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_HYPER is not set[/B]
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_LULZACTIVE is not set[/B]
[B]# CONFIG_CPU_FREQ_DEFAULT_GOV_KTOONSERVATIVE is not set[/B]
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
[B]# CONFIG_CPU_FREQ_GOV_ONDEMAND_FLEXRATE is not set[/B]
[B]CONFIG_CPU_FREQ_GOV_INTERACTIVE=y[/B]
[B]CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y[/B]
[B]CONFIG_CPU_FREQ_GOV_ADAPTIVE=y[/B]
[B]CONFIG_CPU_FREQ_GOV_PEGASUSQ=y[/B]
[B]CONFIG_CPU_FREQ_GOV_SMARTASS2=y[/B]
[B]CONFIG_CPU_FREQ_GOV_HOTPLUG=y[/B]
[B]CONFIG_CPU_FREQ_GOV_LAGFREE=y[/B]
[B]CONFIG_CPU_FREQ_GOV_HYPER=y[/B]
[B]CONFIG_CPU_FREQ_GOV_LULZACTIVE=y[/B]
[B]CONFIG_CPU_FREQ_GOV_KTOONSERVATIVE=y[/B]
[B]# CONFIG_CPU_FREQ_GOV_SLP is not set[/B]
# CONFIG_CPU_FREQ_DVFS_MONITOR is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y

0.3.1

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_TABLE=y
CONFIG_CPU_FREQ_STAT=y
# CONFIG_CPU_FREQ_STAT_DETAILS is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_INTERACTIVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_ADAPTIVE is not set
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
# CONFIG_CPU_FREQ_GOV_INTERACTIVE is not set
# CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set
# CONFIG_CPU_FREQ_GOV_ADAPTIVE is not set
# CONFIG_CPU_FREQ_DVFS_MONITOR is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y

Rest of changes for governors are documented here:

https://github.com/garwynn/D710SPR_GB27_Kernel/commits/master/drivers/cpufreq

I'm honestly surprised all of this is happening. Never seen this before from just enabling stock governors and adding new ones.

If the issues still occur in 0.3.1 I will have to suspect something else at play - maybe in the ramdisk?
[Samsung Epic 4G Touch] PanchoPlanet:
Cerj, what rom / mod are you running. ?

Pp.:beer::thumbup::)

From the Epic Touch that shoots jelly beans ..... into your ..... eye ..... phone!
[Samsung Epic 4G Touch] cerj:
JellyVerse v2.0, no mods. Its plenty fast, and DS battery saver comes with, so batt is good. I may try Exit_Only's newest to test. I have never used KO's or Goddly's tweaks so I havent had any issues with any of the new kernels from garwynn
[Samsung Epic 4G Touch] Mattix724:
I can confirm the fix with 0.3.1 running Jellyverse 1.0 with Comodose 1.3 installed.
[Samsung Epic 4G Touch] PanchoPlanet:
I guess it comes down to that init.d folder being present.

Going to delete folder and start over. Thanks. :)

Pp.:)

From the Epic Touch that shoots jelly beans ..... into your ..... eye ..... phone!
[Samsung Epic 4G Touch] Mattix724:
Flashed using Mobile Odin over 0.1 kernel.
[Samsung Epic 4G Touch] dataman:
Works great on kobridge ROM. all the tweaks included, + TD's AIO.

I did not delete or modify any of the tweaks or int.d etc

Thanks
[Samsung Epic 4G Touch] PanchoPlanet:
Is the fix supposed to bypass the init.d issue.

If it does that mean I can leave folder in place for Kobs rom / td's AIO mod?

Pp.:beer::thumbup::)

From the Epic Touch that shoots jelly beans ..... into your ..... eye ..... phone!
[Samsung Epic 4G Touch] astolenheart:
Awesome job

Sent from my E4GT in the minecraft world :p
[Samsung Epic 4G Touch] dasesq:
Flashed 3.0 zip all is well on sgs4 1.1. Also 4g speeds above 13000
[Samsung Epic 4G Touch] Mattix724:
I don't really know, garwynn knows what's different between 0.3.0 and 0.3.1

I have TD's AIO and Comodose 1.3 and it just worked without touching the init.d directory.
[Samsung Epic 4G Touch] jaxon01:
The 0.3.1 has all of the custom governors removed that were in 0.3.0. Therefore you can leave everything in place.

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] dataman:
If you read couple of posts up you see that v2 and v3 both had issues with Kobridge and init.d and would go in reboot loop

version 3.1 fixed that.

---------- Post added at 01:28 PM ---------- Previous post was at 01:18 PM ----------

Would it be totally crazy to have the touch screen working in the Recovery?
[Samsung Epic 4G Touch] DarkEye45:
I flashed 0.3.1 using Mobile Odin over 0.1.0 kernel and I'm not getting boot loops anymore like I did with 0.3.0. So far so good.

I'm using MIJJz JB GOODNESS JB 4.1.2 FK23 v1.0.3 (Updated 12/21/2012) ROM and have been on it for months.
[Samsung Epic 4G Touch] jaxon01:
I am using v0.3.0 with the extra governors along with Comadose v1.3 Variant and AIO rev3 on TBSGSIV and there are no problems. Just wanted to let people that want the extra governors to know.

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] Mattix724:
Did you install Comodose before or after 0.3.0

The issue that I was reading is the kernel caused bootloops with init.d tweaks already installed
[Samsung Epic 4G Touch] PanchoPlanet:
I think they call it TWRP ?

Pp. :)

Transmitted from another galaxy with a Jellybean infused P-5113 full of Unicorn porn.
[Samsung Epic 4G Touch] garwynn:
OK, I've been reading the tweak threads a little bit and I'm not sure we have to make 2 separate flavors.

Instead just need to figure out what governors are causing the problem and not add them.

Here's what was available in 3.0:

Stock:

PERFORMANCE

POWERSAVE

USERSPACE

ONDEMAND

INTERACTIVE

CONSERVATIVE

ADAPTIVE

PEGASUSQ

Custom:

SMARTASS2

HOTPLUG

LAGFREE

HYPER

LULZACTIVE

KTOONSERVATIVE

Goddly, Kobridge - if you see any that should be removed let me know.

I'll be happy to see if we can find a happy medium.

Once the governor issues are resolved I figure OC and voltage settings would be next.

Agat will work on Extweaks/STweaks support at some point.

Please direct any recovery/ramdisk questions to him and/or me.

Thanks!
[Samsung Epic 4G Touch] PanchoPlanet:
Thanks Garwynn for messing up my phone ................,........ :D just kidding :D

Noooo, really wanted to thank you for this build. :D:D:D

Great work.! And recovery!

Pp.. :D

Transmitted from another galaxy with a Jellybean infused P-5113 full of Unicorn porn.