yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Verified MD5 hashes using Scary Alien's Android File Verifier, v1.40 zip flashed from Helix's .34 mod of your 1.30. Wiped Cache and Dalvik - not sure if I had to. Booted fine, booted back into recovery, flashed CrossBreeder_6.13.13_v3.zip, it wiped Dalvik on it's own, rebooted fine again. My SetCPU settings stuck - PegasusQ and NoOp, 25MHz-1000MHz. Not undervolted at this time.

Hmmm! I think I notice it being lagless. Thanks!!!!! (understatement)

Oh, now to make another Nandroid.
[Samsung Epic 4G Touch] dataman:
Any update on adding hold to scroll?
[Samsung Epic 4G Touch] treyweez11:
just curious as of what settings people are using with this kernel, im running TBGS4 but i keep bouncing back and forth cause im not sure which one is the best.
[Samsung Epic 4G Touch] blackcanopy:
I have been running that the same ROM for a few days now. My setup has been... Ondemand/SIO 25/1400 and getting great battery and very quick. It sleeps like a baby and wakes up to run like a Jaguar after its prey, but doesn't show down to catch it's breath.

Even overclocked to 1400, the ondemand governor utilizes 400/500 second to 25. It'll have a little time around 1000, and very little time at 1400 (unless I'm doing something requiring a load on the CPU).

---------- Post added at 07:54 PM ---------- Previous post was at 07:47 PM ----------

Ondemand and conservative seem to use the low end of the scale slot more frequent, and bounce around midline with just the screen on while reading and such.

Other governors seem to bounce between midline and top end, rarely using the lower end while performing the same tasks.
[Samsung Epic 4G Touch] treyweez11:
Which program are you using to manage your CPU?
[Samsung Epic 4G Touch] blackcanopy:
I use rom toolbox pro for governor/scheduler and over/under clocking. And CPUspy to see how much time is spent in each frequency.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I hate to say this but I've had at least three complete lock ups since flashing 1.40 requiring a battery pull. The first time when I was on a phone call (it's all right I was on hold). I thought it was CrossBreeder that I flashed, so I flashed it's uninstall zip. Then it happened again, this time while typing in TapaTalk, so I restored a backup from before I flashed 1.40 or CB, then re-flashed 1.40. Then it froze again; I forget what I was doing this time.

[MENTION=2953465]agat63[/MENTION], do you want a logcat the next time or wait for other reports first?
[Samsung Epic 4G Touch] remotehugger:
could it be your choice of governor ? I've been using it for the last few hours using smart@ss2/sio - 300/1500 with no problems - did a backup and restore - been playing some angry birds and zombie evil and some light web surfing -

Sent from my Aoikazed by Pio Thrive
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I'm still using the same settings, 25-1000MHz PegasusQ NoOp, no under volting. Hadn't had any luck ups before. Not saying it's the Kernel for sure, I'm just suspicious for now. :)
[Samsung Epic 4G Touch] remotehugger:
yes that's a headscratcher ??
[Samsung Epic 4G Touch] btoddweber:
For what its worth...was using 5.0 and switched to 1.4 and couldn't make a screenshot....swapped back and OK???

Jellyverse with Com a dose 1.3
[Samsung Epic 4G Touch] blackcanopy:
You couldn't take a screenshot using this 1.4 kernel? I'm using this kernel on TBSGS4 and able to take screenshot..
[Samsung Epic 4G Touch] agat63:
Not to defend kernel or anything but kernel has been downloaded 76 times so far and yours is only report of lock up.

It can have different causes.

Rom/tweaks/additional scripts (if any)/governor/scheduler and any of the possible combinations of all of them.

Let us wait for couple of more days and see if this problem persists or more reports will be made.

If more users will have same or similar problems I'll know that's most probably kernel related.

That would be my take on this situation.

Hope you agree with me.
[Samsung Epic 4G Touch] btoddweber:
I couldn't...:confused::confused:guess I wasn't holding my mouth right
[Samsung Epic 4G Touch] btoddweber:
Edit..I'm an idiot...no idea why it wasn't working:thumbup::thumbup:
[Samsung Epic 4G Touch] blackcanopy:
Maybe wrong button combination?? I'm glad you have it another shot.
[Samsung Epic 4G Touch] btoddweber:
No idea..had it charging and WiFi..was taking screenshot with power menu option not home and power.

I guess I fat fingered it....no idea...but thanks
[Samsung Epic 4G Touch] remotehugger:
I have noticed that it takes quite a bit longer to fully boot up on this kernel compared to 1.3 - other than that I haven't had any problems so far -

Sent from my Aoikazed by Pio Thrive
[Samsung Epic 4G Touch] btvolta:
What is Frandom molecule, may I ask?

Update: Nevermind, SG already answered. Thanks
[Samsung Epic 4G Touch] remotehugger:
just had a complete freeze up - screen wouldn't come on - had to hold power button for like 30 seconds to reboot - gonna have to go back to 1.3 till this gets sorted out - :(
[Samsung Epic 4G Touch] btvolta:
Must have something else going on. This kernel is running nice and I even installed the latest cross breeder.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] remotehugger:
idk - didn't have any problems on 1.3 - and I'm just running stock/rooted ROM - no add ons or anything -

Sent from my Aoikazed by Pio Thrive
[Samsung Epic 4G Touch] btvolta:
I wish I could help you. Is it meant to run on stock?

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] remotehugger:
I'm not sure but I would think so since 1.3 runs without a hitch -

Sent from my Aoikazed by Pio Thrive
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I'm completely with you, I have to diagnose things all the time so I believe in the scientific method. :)

Your symptom sounds like the same symptom I had a total of three times with 1.40. In my case I did a battery pull each time, although I'm sure holding down the power button would've rebooted as well. I've gone back to my backup that had Helix's modified version of 1.30 with .34 recovery in it for now. Haven't had any repeats under 1.30.

Edit: What governor, scheduler and over/underclocking and undervolting settings are you using?
[Samsung Epic 4G Touch] BluesRulez:
It seems that folks who have freezing are undeclocked to 25MHz. Can you guys try to see what happens at 100MHz and remove all undervolting?
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I don't undervolt at all yet, but sure I'll reflash 1.40 when I can and test at 100MHz. So you've seen others report the same thing elsewhere and they were all set at 25MHz minimum?
[Samsung Epic 4G Touch] blackcanopy:
I'm always underclocked at 25MHZ without any freezing here while using Agat 1.3 or 1.4.

I know allot of people getting reboots and freezing are using the AIO AOSP lockscreen while having rotation enabled. I'm not sure if the scenario is kernel specific.
[Samsung Epic 4G Touch] btoddweber:
Which AIO? Would that matter?
[Samsung Epic 4G Touch] blackcanopy:
I believe the issue started around V3.0 and still present in 4.0.

Edit:

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

GB27 All in one Mod V4.0 Updated 05-23-13
[Samsung Epic 4G Touch] btoddweber:
Meant is the AIO version consistent with the issues arising? Like is everyone on 3.5 or 4.0? Just wondering
[Samsung Epic 4G Touch] jayhi74:
1.4 locked up on me once today as well Running AIO 4.0.

sent from the Deucefo24 block
[Samsung Epic 4G Touch] blackcanopy:
the issue seems to affect all versions from 3.0 to 4.0

---------- Post added at 12:22 AM ---------- Previous post was at 12:14 AM ----------

I'm using Agat 1.4 kernel and the AIO 4.0 with TBSGS4 ROM, underclocking to 25MHZ overclocking to 1400MHZ SIO/ondemamd and haven't has a freeze or reboot that wasn't user error (undervolting too much). The only time I had a reboot was after testing the pegasusq kernel, and that was a one time thing on Agat 1.3.
[Samsung Epic 4G Touch] jayhi74:
Hmmm I never underclock, straight no chaser! Lol 100-1200, sio ,smartassv2 so I dunno?

Edit make that 200-1200 haha see too much straight no chase!

sent from the Deucefo24 block
[Samsung Epic 4G Touch] mradlauer:
Smartassv2, 25mhz-1000mhz and noop...

No problems here.

Using TDs recalked and 1.4.
[Samsung Epic 4G Touch] tdunham:
Locked up how exactly?

Like has been said they're is a big with aosp lock screen in combination with having rotation enabled that is causing freezing. Not the kernels fault, just pointing it out again.
[Samsung Epic 4G Touch] jayhi74:
Yo TD, thanks I am aware of those issues and I don't use AOSP Lockscreen or rotation. It locked up opening a picture in Picsart app. Just happened once, it's been running fine since then.

sent from the Deucefo24 block
[Samsung Epic 4G Touch] roirraW "edor" ehT:
For the record, I have the lock screen disabled and I'm using Widget Locker (with rotation) with never a problem under 1.30 (just repeating to have all the info in the same place) 25-1000MHz PegasusQ NoOp no undervolting.
[Samsung Epic 4G Touch] Sloth:
agat congrats on the new title :D:beer:

Sent from my Eliptic Nexus 7 :p
[Samsung Epic 4G Touch] Stryke_the_Orc:
+1 Definitely deserving of it:D:beer::thumbup:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] jdsingle76:
+2....I'm surprised it took this long! Congrats Agat! ! ! :thumbup::beer:
[Samsung Epic 4G Touch] prguzman1978:
About time Agat you get a title you deserve it!!!
[Samsung Epic 4G Touch] BluesRulez:
Those who want the updated kernel in one click format. Agat_GB27_v1.4.0.exe - 6.18 MB
[Samsung Epic 4G Touch] tdunham:
Thanks Bluez having these one-clicks available is always a lifesaver.
[Samsung Epic 4G Touch] svicenty:
Always been the man agt
[Samsung Epic 4G Touch] CyberpodS2:
Yah, I have one-clicks ready on all my systems... keeps the stress down when crap goes wrong. Lol
[Samsung Epic 4G Touch] agat63:
Thanks for support, vote of confidence and congrats...:victory:
[Samsung Epic 4G Touch] etd:
I have been on 1.4.0 for almost a day and I must say, it is very smooth! Thanks a bunch agat!!!
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I haven't re-tested 1.40 yet, nor raised my minimum from 25MHz to 100MHz as someone suggested. I notice that in 1.30, my phone spends a good 9% of the time at 25MHz and I never have a problem, so I was wondering if it's considered an issue if 25MHz doesn't work correctly under 1.40, and may be identified and fixed in the future?
[Samsung Epic 4G Touch] Samsung Fanboy:
From my experience 25MHz no undervolt caused my phone to be unresponsive and then it just reboots. I found 200MHz to be the lowest I can go without any problems.

Sent from my V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] remotehugger:
I wasn't under clocked at all - I was running 300/1400 and was freezing up on 1.4 but not on 1.3
[Samsung Epic 4G Touch] agat63:
That's very strange.

I didn't do any changes or edits to kernel source in 1.4.

I did add frandom module and it's done in ramdisk.

Only change to kernel itself is different compression rate.

Once kernel installed/flashed it should not affect anything.

I can try to compile with previous compression rate and see if if makes any difference but I don't think it would.
[Samsung Epic 4G Touch] remotehugger:
of I'm the only one having issues don't waste your time agat - 1.3 is running strong and stable - but if you wanted to give it a shot is def. flash it and see what happens - none the less, thanks for the offer ! very cool :D
[Samsung Epic 4G Touch] Stryke_the_Orc:
FWIW, I'm getting random SOD on a previously stable setup. Haven't been able to pinpoint what's causing it yet, when I do I'll report back if was kernel related or not:beer:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] CyberpodS2:
I also had one sod on 1.4.0 and since I'm on vacation choose to just go back to 1.3.0 for now. Like you I did not notice the circumstance in which it occurred.
[Samsung Epic 4G Touch] Stryke_the_Orc:
It just happens randomly. I can turn the screen off and right back on and its fine 99.9% of the time, or I can go hours with screen off with same results. I'm wondering if it has to do with the frandom (sp?) module. Thats the only other thing I've changed.

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] blackcanopy:
Maybe the F in frandom stand for

"Freeze" at random... Lol

Edit: was your case with or without CrossBreeder installed?
[Samsung Epic 4G Touch] Stryke_the_Orc:
With it installed, this kernel was the whole reason I installed the tweaks:beer:

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] ardianz:
Using v1.4 On ko rom+aiomod v4+CB+ko tweak aggresif,smartassv2,sio, 200-1000mhz...get freeze/SOD two time...get back to v1.3
[Samsung Epic 4G Touch] roirraW "edor" ehT:
FWIW, I tried 1.40 both with and without CrossBreeder flashed and had the same lockups either way.
[Samsung Epic 4G Touch] tdunham:
Sleep of death or while using it?

I've got to flash this but can't do it during the work week. Too important to have 100% working. :)
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I think both. While using it the first and third time and I think SOD the second time.
[Samsung Epic 4G Touch] tdunham:
Which ROM(s) does this happen for you again (and anyone else having this issue)?

The wife is leaving for a couple of weeks so I'll be able to do a little extra testing while she is gone. You guys know how it is... :rolleyes:
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I've been using Kobridge's deodexed GB27, the AIO 4.0, the 3Minit exported app, the silent camera and CSC tweaks, and the loud audio mod. Been working great under Helix's modified Agat63 1.30 kernel (removed Adaptive I believe).

Good luck with your testing!
[Samsung Epic 4G Touch] CyberpodS2:
In my case, WOR 4.0 and it ran for over a day and a half before SOD occurred. I noticed it was hot in my pocket. Running 100-900 / pegasusq-sio. No issues since returning to

1.3.0 but I'll report back of I have any reason to believe it could be anything other that the kernel change. This install has been stable for like 6 weeks.
[Samsung Epic 4G Touch] dataman:
SOD at the end of the calls once a day or so. Going back.

Sent from my SPH-D710
[Samsung Epic 4G Touch] BluesRulez:
I have 3 logcats. These are upto right before the phone freezes and I have to restart phone.

https://www.dropbox.com/sh/c45rxzpousn3m8h/gw6j0Rl3_m
[Samsung Epic 4G Touch] agat63:
Did compile kernel with original compression rate.

Let's see if it changes anything.

Links taken down.

Kernel did not boot.

I don't expect it to make any difference but let us make sure that compression rate didn't cause it.
[Samsung Epic 4G Touch] cramer18:
tried the 1.4.1 zip file phone will no longer go past splash screen, also will not go into recovery.

running JV v3.0

edit: Odin back to 1.3.0 everything is good.
[Samsung Epic 4G Touch] agat63:
Thanks for heads up.

Taking links down now.
[Samsung Epic 4G Touch] agat63:
Let's try it again.

AGAT_GS4_v1.4.1.tar

AGAT_GS4_v1.4.1.zip

I did flash tar and phone is booting.

Can't say more tho.
[Samsung Epic 4G Touch] leaderbuilder:
Assuming you meant GB27 and not S4. :p
[Samsung Epic 4G Touch] agat63:
You assuming right.

Flashed GS4 to my phone few min ago.... Still typing same name..

But uploaded files are GB27....:p

Edit: I won't rename links in my post so this conversation makes sense... :D
[Samsung Epic 4G Touch] leaderbuilder:
Flashed latest.tar no freezes, cleared both caches. A few reboots and all okay. Then tried nandroid and our locked up just after preload, twice... I'll try the zip
[Samsung Epic 4G Touch] blackcanopy:
I'm sure you've already considered, but, you do have plenty of room on your SD correct?
[Samsung Epic 4G Touch] leaderbuilder:
Oh yeah, 12 GB. Flashed back to 1.4 and created nand no problem.
[Samsung Epic 4G Touch] agat63:
Nothing in recovery should be affected in new kernel.

All I did is change compression rate.

Nothing else have been edited...
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I just flashed 1.41 and am making a backup now. I had wiped cache and Dalvik before rebooting back into recovery, without booting the ROM so I'll probably make yet another backup after booting the ROM just to cover all possibilities. I'll continue to test in all possible ways.Thanks, Agat63!!!

Edit: progress report, still backing up and it's gotten past the backing up of preload. FYI I'm backing up to external SD.
[Samsung Epic 4G Touch] remotehugger:
if your backup and restore completes I will flash 1.41 and report any bugs as well -
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Backup complete. I'm letting it boot up now, it's optimizing the apps since I cleared Dalvik. I'm not that worried that it won't restore, I'm mostly concerned with finding out if it will freeze any more, and I'll try CrossBreeder. I'll do a restore test later when I'm done playing with the fun stuff. :D
[Samsung Epic 4G Touch] prguzman1978:
Flashed kernel 1.4.1 and no problems so far, what is the default governor cause when i checked it displayed pegasusq/sio?
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Did you check the MD5 Hash of the files that you downloaded on your phone and compared them to the download pages for them?

Edit: Flashed CrossBreeder (old version because I forgot to check for new version), everything good so far.
[Samsung Epic 4G Touch] leaderbuilder:
Always do - on PC and on phone.

Flashed 1.4.1 zip. Created Nandroid and verified via AFV app (havent done full restore yet).

Cleared both caches - all OK.

Installed from zip all OK

No issues with applications. Speed is good.

No freezes or anything but it's early.
[Samsung Epic 4G Touch] btoddweber:
Links are not pulling right this is what popped up whenever I clicked on the zip link
[Samsung Epic 4G Touch] agat63:
Just tried both. Both links are working.

Your screenshot shows something completely different.

Wrong file name, wrong size, wrong author....:confused:
[Samsung Epic 4G Touch] remotehugger:
so far so good on 1.4.1 - nandroid and restored fine - running at 200/1400 sio/smart@ssv2 - besides the still longer than 1.3 boot times all is well ! :thumbup:
[Samsung Epic 4G Touch] agat63:
Bit longer boot time can be related to frandom module.

On boot kernel checks if module is present and insmod (loads) it.

Except for frandom module and upgrade to latest linux version there are no other edits or changes to kernel.
[Samsung Epic 4G Touch] btoddweber:
So pg 1 is OK...it showed 1.40 not 1.41 that's why I tried the post 3 pgs back right below where you said link taken down...

Sorry
[Samsung Epic 4G Touch] agat63:
I haven't posted links on pg 1 (OP) yet.

Let's make sure this kernel works as it should and if there are no problems with it I'll post it on page one.

Until than this is the post to be used for 1.4.1:

http://xdaforums.com/showpost.php?p=42722259&postcount=455
[Samsung Epic 4G Touch] jt_hatch:
I've been having SODs and random freezes with 1.4.0 + CrossBreeder as well. (Running on JB Blu Kuban.) Seems like it didn't do it at first but has been happening a couple times a day for last few days.

Trying out 1.4.1 now; will report back.
[Samsung Epic 4G Touch] gamepro602:
Wasn't adaptive and interactive one of the govs. In this kernel, because I don't see them
[Samsung Epic 4G Touch] agat63:
It was Adaptive governor that was causing hang.

I disabled it. (I think)...:rolleyes:
[Samsung Epic 4G Touch] remotehugger:
ty for the explanation - its def. not an unbearable amount of time - just noticed it was a bit longer - still so far so so good - I've let the phone sleep by itself and put it to sleep and no sod's - :D
[Samsung Epic 4G Touch] prguzman1978:
I tried switching to smartassv2/sio and 10 minules later my screen wouldnt turn on it SOD style went back to the new infamous governor pegasusq, besides that no problems...
[Samsung Epic 4G Touch] remotehugger:
damn - twice in a row I froze opening dolphin browser - had to hard reboot both times - not sure about this - lol - will keep an eye on it -
[Samsung Epic 4G Touch] helix4u:
Time to give this a whirl I guess... :laugh: Oh man, I need to get on this forum more often...

Looks good so far. Now, if I only had a signal in this building, that'd be nice.... I guess its my own fault. I have a closet full of wireless AP's sitting next to me.

I'll throw it through the regular tests and watch for SOD.... but I might mention that I've seen SOD once, maybe twice on 1.3.0 as well... but it hasn't bothered me enough to look into the cause.

Update 1: All the usual test look good. Backup/reboot/wipe/etc. look good. Frandom + installing crossbreeder is looking good. Nothing unusual to report. Remotehugger, dolphin browser is working fine here... no freezing. Maybe try reinstalling the browser or clearing the data/cache for the app. If anyone having an issue that they want me to try and reproduce or want me to repack with black background instead of stitch background or anything of that sort for giggles just let me know. I'm finally settled down in my new place and have a little spare time to kill again.
[Samsung Epic 4G Touch] blackcanopy:
Is it possible to get interactive governor back in this kernel, or was it one of the problem governors?

Edit: and the issue with conservative governor not able to change the sampling rate min lower than the sampling rate max?
[Samsung Epic 4G Touch] blackcanopy:
Forgot the screenshot...
[Samsung Epic 4G Touch] agat63:
If memory serves I took interactive governor out because it was preventing phone from going into deep sleep.

Just the presence if it was causing it. You didn't have to make it current.

Adding governor back is not an issue and can be done any time but will have to go thru my threads and try to find the reason I took it out.

I remember saying something about it but not sure what thread it was.

As for sampling rate.

I'm using governors made by others I'm not writing them (far above my head).

So anything in the governor itself is out of my hands.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I can't say without a doubt that it's 1.41 but yesterday I flashed it and (later) the latest CrossBreeder and later on I noticed that my phone was either off or SOD (no lights when pushing buttons /screen). Later on the same thing. I restored my backup and flashed just 1.41 no CB. The phone was off again when I took it out of my pocket a little later, and this morning apparently again (my alarm didn't go off) :).

For now am back to Helix's mod of your 1.30. See sig for ROM.
[Samsung Epic 4G Touch] blackcanopy:
I remember reading about it being taken out, but was unsure if was safe to add back. No need to bother with it, i was just going to play around with it because its the governor CrossBreeder tweaks for performance/battery.

i really appreciate your response, i wouldn't know where to begin with building governors. I didn't know if it were just a simple some'n some'n that could be changed.
[Samsung Epic 4G Touch] jt_hatch:
Put 1.4.1 and crossbreeder 6.19.13 on yesterday; ran great for a while, then last night I noticed touch response starting to get very laggy, then the within about a minute the entire system froze. Was able to reboot by holding power button.

Running GB27 Blu Kuban and using ExTweaks -- pegasusq governor, max freq 1.3 GHz, min freq 100 MHz, 25 mV undervolting. Setup is very stable on 1.3.0 kernel (no crossbreeder).

Currently back on 1.3.0 setup for stability. May try out 1.4.1 w/o crossbreeder (though def. noticed improved smoothness and battery life w/ 1.4.x and crossbreeder!) to see if I can isolate whether my freeze issue is kernel or crossbreeder related.
[Samsung Epic 4G Touch] agat63:
Since there are no other changes in kernel except main stream updates I really start think that all this problems are caused but frandom and CB.

It's good idea to run 1.4.1 without CB just to narrow it down.

If you still have freezes and other hick ups I'll go back to previous Linux version as in 1.3.0 and try it again.

I can add fandom to 1.3 without running update patches and we will see if it's frandom, patches or combination of both...