yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] MoHoGalore:
Ok.. somethings wrong.. I'm going to leave it to you guys to tell me..

Before: Complete stock, no root, gb27

Flashed the 0.3.13 GB27 with tRec to flash a test build..

What I want you to look at is that I had the red notification light before I turn the phone on.

I can recreate it by turning the phone off and having someone send me a gtalk msg..

What.. The.. Frack..

it's a tad large but here is the video.. http://d-h.st/c8k
[Samsung Epic 4G Touch] leaderbuilder:
That was weird! Pretty bright too.

Was that on first boot after Odining the kernel or on all power ons?
[Samsung Epic 4G Touch] MoHoGalore:
I can turn the phone off, ask someone to gtalk me and it comes back each time..

It's a first for me. No way for me to know if the phone is actually powered off but the power on screen is pretty definitive..
[Samsung Epic 4G Touch] Mattix724:
Maybe we now have sleep mode on Android lol! I'll have to try this out.

---------- Post added at 06:48 PM ---------- Previous post was at 06:28 PM ----------

Btw I could not recreate the bug. My E4GT only gets data over Wi-Fi though.
[Samsung Epic 4G Touch] PanchoPlanet:
Moho, waiting for huge video file to finish d/l, I was going to ask why isn't this being tackled on a pure stock rom platform, instead of non stock rehashed roms?

All the different roms and tweaks don't give you a control to work with.

I just saw video, that's wack!

Pp.:confused:

Sent from an Epic Touch that shoots jelly beans into your .....eye .... phone.
[Samsung Epic 4G Touch] MoHoGalore:
I'm wondering if it's just not a phone issue. It is a replacement from my original. But still doesn't make any sense.

It's a titanium that replaced my stolen original black.

I'm seriously confused with this issue.

I did flash back to gb27 stock and it doesn't do it. About to go back to 3.13
[Samsung Epic 4G Touch] Raistlin1:
Been using 3.1 and my kernel usage has gone from 6% up to 15% with normal usage. Also, the reboot and drop into the teens for battery percentage started happening to me on this kernel. I have not had this happen since I used an agat source/repack kernel back on ICS and it never happened stock GB27 kernel. Other than that I have not seen any hiccups using this version of the kernel as a daily driver besides the battery usage jump from the stock kernel.
[Samsung Epic 4G Touch] MoHoGalore:
Guess I'm confused on your question. It was pure stock GB27 with the added GB27 0.3.13 after.

In case you're wondering how I got to stock, I went back to FL24 and used Kies to take it to GB27.

Is that what you were asking?
[Samsung Epic 4G Touch] helix4u:
Been running it all night like this. No issues.

Side note on reboots while doing backup: While I was at work today I left the phone in recovery for an extended period of time and at some point it rebooted... so I'm not entirely convinced that its a reboot while doing a backup issue... it might just be a reboot after being in recovery for so long issue... I didn't try to reproduce the issue to confirm, but there's that, for what its worth...
[Samsung Epic 4G Touch] tt281gt:
I had the same issue. Went back to 3.0 and it seems better but still too early to tell regarding kernel usage.
[Samsung Epic 4G Touch] leaderbuilder:
Seems like it's an actual hardware issue. I know that must of, if not all replacements, are refurbished units. Maybe try an FL24 one click full restore/data wipe and see if it persists. Then if it doesn't flash a one click or the tar. I don't know just reaching.
[Samsung Epic 4G Touch] MoHoGalore:
Doing that as we speak. Kies is taking forever so the rest will have to wait until tomorrow.
[Samsung Epic 4G Touch] PanchoPlanet:
What I mean is, Garwynn is making and remaking changes in reaction to all the issues that we have with out phones and according to what Roms and tweaks.

Wouldn't it be simpler if it gets refined on a pure stock rom, then afterwards you can modify it according to build type.

Just a thought. :)

Pp.:):thumbup:

Sent from an Epic Touch that shoots jelly beans into your .....eye .... phone.
[Samsung Epic 4G Touch] helix4u:
Bare with me, I'm still learning...

While I was messing around today I found that the lines you mention above were among the lines that didn't play well with sysctl -w kernel.hung_task_timeout_secs=30 & sysctl -w kernel.threads-max=524288... more specifically tested was sysctl -w kernel.hung_task_timeout_secs=30... I just took out sysctl -w kernel.threads-max=52428 because I had to get back to work and it was the only line left that I was unsure about... I became suspicious that sysctl -w kernel.hung_task_timeout_secs=30 was the issue because the phone booted, then after a period (30-ish) of time it borked up and rebooted and the line mentions a timeout of roughly that amount of time. So what I'm trying to achieve is the most minimal changes to KO's tweaks as I possibly can... to try and keep as much of the battery/performance tweak-ness around as possible. So, while removing the lines you did seems to do the trick, it's also changes the way processes interact with each other, memory, process scheduler behavior. I believe that all that kernel.hung_task_timeout_secs=30 does is says that if a process has been sitting for more that 30 seconds, then kernel panic/reboot the device... Seems to me like a less invasive change. So I guess my question for you is, if you remove only the two lines I mentioned above in 4.2, is it still stable? No reboots?
[Samsung Epic 4G Touch] Goddly:
I understand , what I did , was strip the script down , started with hot plugs, sleepers, reboot s still occurred, then keeping with a kernel issue went thru the sysctl kernel tweaks, removed them all, ran fine added back added back etc,
[Samsung Epic 4G Touch] helix4u:
Same... minus the hotplugs tweaks. I removed the "other" entire section, then went through running the command in top-down order via ADB as su until I found the problems. Then did the same test staring from the bottom of the list... What I noticed was I could keep the commands you pointed out if I removed the timeout and max threads (max threads still questionable if it needs to be removed). I'm just wondering if the same can be done in the 4.2 tweaks.
[Samsung Epic 4G Touch] Goddly:
My only problem is the panic and reboot is for when something's not right, removing it may solve the paniic reboot, but the issue causing it may be left unfixed.,,,, know what I'm saying?
[Samsung Epic 4G Touch] helix4u:
Yeah. Makes sense. I'm also questioning that if hotplug is working and disabling one of the cores... if the timeout just needs to be higher.
[Samsung Epic 4G Touch] Goddly:
A few of the hot plug Ines call on sys hot plug etc etc. Which the file called on doesn't exist where its directed.. At least on 3.0 the files not there,
[Samsung Epic 4G Touch] helix4u:
I see.. thanks man. The learning continues! :)
[Samsung Epic 4G Touch] btoddweber:
So running kob deodex w/ tweaks..if u del kob41 all should be well to use cr kernel?
[Samsung Epic 4G Touch] boXerrumble:
I'm pretty sure, after reviewing this entire thread, that 0.1.0 is the most stable kernel version thus far, despite it being basically stock with CWM, on older Linux 3.0.31xxx, and being without governors.

All the other versions have issues working with tweaks, and issues with making backups.

Went back to 0.1.0 today, and have had no issues. Does feel smoother than the stock GB27 kernel, and I've had slightly better battery life on it.
[Samsung Epic 4G Touch] cral:
I second that, JellyVerse with 0.1.0 and Comadose tweaks had the best battery life. I tried the others kernals with the tweaked Comadose to get them to work together to get it snappier but my battery was draining faster. I guess back to 0.1.0 with the original Comadose tweaks. Hopefully they'll work out the kinks soon.
[Samsung Epic 4G Touch] sai5o4:
IMO, I'm running Jellyverse with 0.3.0 and no tweaks and battery life has been amazing! With pegususq as governor, deep sleep batt. drain is almost non-existent. Phone was on a day and some hours and it was still kicking.
[Samsung Epic 4G Touch] SASQUATCH:
Installed 0.3.0 kernel but can't change governor :confused:

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] Goddly:
3.0. With Pegasus is amazing on battery.. I've been flashing 100 diff things and trying to help KO figure out his tweak.So ive not had much time to test govs yet.. alsi like ktooncervative.... But To let you all know, it was only 5 lines of script from KO's 41_tweaks script . that was throwing phone in reboot after about 45 - 1.30 seconds after boot, which was the only problem i could find... other than a few hotplug lines not doing much , files called for were non existent .. unless Helix , Garwynn or Kobridge has anything to add, im pretty sure were done here. ... ;) great work Helix , Ko, my testers.. And a Big thanx to Sextape ;) for pam and tommylee, kim kardashian and ... oh wait. Lol. For all the leaked kernels, modems, source releases. Another big thanx to Garwynn for the custom kernel work, Agat for repacks, and source recovery. Seeing how GB27 is the final for our E4GT , Im sure your work here is about up.. hope to see you guys on greener pastures.. THANKS AGAIN.
[Samsung Epic 4G Touch] SASQUATCH:
Were in the hell are you guys getting this 3.0 with pegasus. I can't seem to find it.

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] Goddly:
lol wha? you gotta cahnge govs, using rom toobox etc, might have to scroll the list to find it..
[Samsung Epic 4G Touch] SASQUATCH:
This is why I'm asking that's all the govs it shows.

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] svicenty:
Hey goddly are does the settings you recommend and what should i use if I want to overclock tegrak?
[Samsung Epic 4G Touch] SASQUATCH:
Got it re dl 3.0 all is good

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] helix4u:
Ha, thanks man.

Yeah, the script issues have been isolated, so in that aspect, we're pretty much done. For me, being the noob that I am, I'll still be messing around for a while just to try to understand more...
[Samsung Epic 4G Touch] btoddweber:
So 3.0 is ok with Comadose v1.3 modded?
[Samsung Epic 4G Touch] helix4u:
Yeah I think he points out the one to use in the comodose thread's OP where he removed the 41tweaks_kobridge script.

3.0 still has recovery issues though.
[Samsung Epic 4G Touch] Goddly:
yessir i have completely removed ko's 41 script.. that was the quickes and easiest fix at the time.. ive since edited the script to a working / stable condition. though havent pushed it back into 1.3... ive got it implemented in 1.4, however , i still havent recieved permissions to use the CrossBreeder mod...
[Samsung Epic 4G Touch] PanchoPlanet:
Hey Squach, by looking at your screenshot I can see that your running td AIO mod, what rom are you running with that?

I was trying to install while on Kob's de-odexed gb27 w/td's AIO mod and it was a no go from the beginning. Boot loops instead of froot loops, frozen boot screen, even tried without mod, I gave up. :banghead:

TIA.

Pp.:thumbup::)

Sent from an Epic Touch that shoots jelly beans into your .....eye .... phone.
[Samsung Epic 4G Touch] Goddly:
i havent been able to test anything too much, i was having good luck with the MODDED 1.3 with pegasusq ;) i like Ktoonservative also
[Samsung Epic 4G Touch] svicenty:
I'm on 3.0 every time I do a backup it fc it never finish when it starts it says error with cache something like that
[Samsung Epic 4G Touch] Goddly:
Thats Ramdisk. (Mounting related) Recovery Related, Thats Agats dept, hes aware of all the issues and will be monday at the earliest for a fix. Again nothing to do with the kernel itself..
[Samsung Epic 4G Touch] garwynn:
Finally could test and found another potential issue. If clear data in 0.2.0 recovery it goes into boot loop, keyboard missing or other odd behaviors. Haven't tested 0.3.0. Repack from Agat seems best for backups at the moment.
[Samsung Epic 4G Touch] Goddly:
Or EL26-29.tar and Mobile Odin with stock kernel.zip on sd, to flash back to rom, because the repack has other small issues also, (paid apps not usable in some cases)
[Samsung Epic 4G Touch] CyberpodS2:
Just to verify, if we use the el26 method with a kernel.zip we will then still need to flash the rom before restoring the nandroid to correctly populate the preload right?
[Samsung Epic 4G Touch] cerj:
Im not sure what your asking. but I restored a nandroid I made with garwynns GB27/agat recovery, without flashing the rom first. I made the nan with the same kernel. Either 1.0 or 3.1. They both worked. I did NOT wipe anything before restoring the nandroid, in all the nan tuts I have read, none say wipe, factory reset or format system, so I dont
[Samsung Epic 4G Touch] Goddly:
wiping!? for a nandroid?
[Samsung Epic 4G Touch] cerj:
Exactly!
[Samsung Epic 4G Touch] Goddly:
negative a nandroid backup is a mirrored image of your System/data cache/dalvik etc, whatever is there is a perfect copy of your current setup, though i have had weird md5 mismatch, kinda frustrated me. but i save backups ;)
[Samsung Epic 4G Touch] Thumper333:
Don't know if anyone else is experiencing this but on any of the kernals except stock and 3.1 I get a spontaneous bootup if I power down phone and connect to charger. Within 5 to 10 minutes the phone just boots. So I stick with 3.1
[Samsung Epic 4G Touch] cerj:
It is a known issue caused by Hotplug and a few lines in some tweaks. I think Goddly and others have got to the bottom of it and narrowed it down. If using Goddly's comadose tweaks there is one that will work.
[Samsung Epic 4G Touch] SASQUATCH:
I'm running jellyverse 2.0 with comadose tweaks. Td aio mod already baked in the rom.

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Samsung Epic 4G Touch] leaderbuilder:
I think CyberpodS2 may be right here.

If you are wiping - like switching between ROMs; especially between a TW then an AOSP/CM and back I've had to flash the ROM 1st then flash tne nandroid on all the JB builds.

I've got like five or six folders for different ROMs(KOs, Jellyverse,T B SGSIV,TouchWhizDreamV5.1, SuperNexus etc.) on my SD so that if I flash between them I can quickly flash that ROM and then flash the nand.

However staying on the same build and restoring has not been an issue - with the kernel repacks that actually do a full nand.

This is just my experience though.

I too am a backup freak. Backup my backups then back those up. :D
[Samsung Epic 4G Touch] Goddly:
Aplologies. Ive not had any issues. Though ive not run aosp at all since ive got the phone 4 months ago.
[Samsung Epic 4G Touch] CyberpodS2:
Edit: It;s all too confusing some days... LOL But yea, as leaderbuilder said it was changing roms was an issue when using el26 for the recovery. --> http://xdaforums.com/showthread.php?t=2055950

It was in response to the reference to using the el26 kernel that I quoted from. I was just hoping to save someone the trouble of restoring a backup only to find parts missing or broken. I know if you use the JB kernels that work it's not needed to flash the rom. But if you use the el26 I was under the impression that it does not restore the preload or something like that.

Once we get this source kernel & recovery squared away all this will be history anyway...
[Samsung Epic 4G Touch] CyberpodS2:
Yea, I guess the JB AOSP roms are compatible with the older recovery versions.

Quick off topic: If your bored some day, you might wanna look at a couple aosp just for sh|ts and giggles... There are a couple very solid roms out there on that side of the fence too. :) My personal fav's are Baked Black Bean 8 and PIB. That said I am totally hooked on WOR right now! :)
[Samsung Epic 4G Touch] Stryke_the_Orc:
Has anyone noticed that wiping data will cause boot loops? I've given my rom out for testing and wiping caches its fine, wipe data and it boot loops. Tried on multiple versions of the kernel 1, 2, and 3 (haven't used any of the newest ones yet)

Just curious if anyone else saw this at all?
[Samsung Epic 4G Touch] g_ding84:
Your not the only one. Same here.
[Samsung Epic 4G Touch] Stryke_the_Orc:
Good to know its not my rom then lol. In order to flash properly had to use same methods as original jb leaks. However the Rom runs fine with the kernel if you flash it after the Rom

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] svicenty:
Hey orc how's your rom coming out
[Samsung Epic 4G Touch] helix4u:
Pretty sure this is a personal record for me... didn't used to even make over 8-10hrs. Using 0.3.0, pegasusq on KO's deodexed, modded 4.3A tweaks.
[Samsung Epic 4G Touch] CyberpodS2:
Yea, it was mentioned about 0.2.0 but I guess it's more than that...

http://xdaforums.com/showpost.php?p=40025623&postcount=318
[Samsung Epic 4G Touch] Stryke_the_Orc:
Redoing the theme I lost, fixing a few small things here and there. Hoping to have another test version soon:thumbup::D

Slithering from the nether regions of a twisted mind and tarnished soul
[Samsung Epic 4G Touch] Goddly:
lol... yea, theres a few Ramdisk bugs out there ... as stated before, Agat was notified , and will release an update around monday (at the earliest)
[Samsung Epic 4G Touch] Goddly:
oh!!!! ??? you want stats!?............ ill give you stats... :D

today ;) W_O_Rv.2 modded 1.3 ComaDose Ktoonservative gov /noop.... Ext. battery... no greenify, no stop services, Ds batt saveron balanced.. All apps included with rom. Havent had time to set them all up..

.
[Samsung Epic 4G Touch] helix4u:
:laugh: Nice... :) Yeah, you definitely win. I'm on the stock battery... OooLllDdd battery. I bought the phone right after it came out, so I'm probably due for a new one soon.
[Samsung Epic 4G Touch] Goddly:
5$ extended battery is what im using... 5$! delivered!
[Samsung Epic 4G Touch] helix4u:
Sounds like its time for me to get on amazon...
[Samsung Epic 4G Touch] btoddweber:
Am I correct in that 3.1 is stock with cust recovery?
[Samsung Epic 4G Touch] blackcanopy:
I believe Linux update as well...

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] helix4u:
Nope. it has linux upgrade. I think 1.0 was stock source built with custom recovery.

I got ninja'd
[Samsung Epic 4G Touch] Goddly:
yea man for real for 5 dollars it comes with the back plate and everything.. buy 3 if you want? for back ups..

My otterbox mod thread has links to the battery with a review
[Samsung Epic 4G Touch] helix4u:
aaand purchased. :victory:
[Samsung Epic 4G Touch] Goddly:
dude for 5 dollars.. ive been trying to tell eevryone.. buy 3 if your worried youll get a bad one... thats the price of a big mac? lol sorry if it sounds like im going off, but i cant get over it.. oh and i came like 5 days before it was supposed to be there, course im on the east coast.. lol
[Samsung Epic 4G Touch] helix4u:
If it were Amazon Prime eligible it would be all the more awesome... ended up being 8.70-something I think with shipping, but still... I have more change than that in my car.

...guess we should probably stay a little more on topic in the thread here... XDA should maybe implement a chat widget of some sort to help keep these types of spin-off conversations from cluttering threads... in any case, thanks for the bada** link.
[Samsung Epic 4G Touch] Goddly:
*touche
[Samsung Epic 4G Touch] JCred:
I'm slightly confused- running 3.0 and see every governor except hotplug, which seems to contradict the directions given after the incremental versions.?? That being said, ktoon and Pegasus both deliver on battery life, but Pegasus has noticeably less lag.

Question: what scheduler are you guys using and why?
[Samsung Epic 4G Touch] leaderbuilder:
On demand and noop. Or Pegasus and noop for me. Ktoonservitive also has done well too. I too am getting freaking great battery - 1 day plus with loads of on screen time, calls etc.. I appreciate the battery a whole lot, but I'm primarily a performance guy.
[Samsung Epic 4G Touch] helix4u:
I'm using noop because of past experiences with it being good... uses the least cpu cycles during I/O...

Here's some good reading on this stuff... http://xdaforums.com/showthread.php?t=1369817

http://xdaforums.com/showthread.php?t=1736168

http://xdaforums.com/showthread.php?t=2005306
[Samsung Epic 4G Touch] SelfElevated2:
I'm getting kernel panic mode!!! I havent seen it do it while the phone is in my hands. When I turn the phone off and plug it in at night I wake up with it in kernel panic mode. Ive had the same issue with the GB27 source kernel on 2 different roms now. TBSG IV and jellyverse which I'm on now. Both GB27

Just thought id mention it. Thanks for the kernel garwynn
[Samsung Epic 4G Touch] btoddweber:
Whenever I get into rom toolbox lite..I select gov..pegasusq...reboot and come back and its ondemand...how do I get it to stay?
[Samsung Epic 4G Touch] SelfElevated2:
Update:::

I decided to test if I could make the issue happen on demand. I turned phone off plugged into charger and went outside to smoke. Before going outside it appeared to be charging normally with phone off. When I came back in 5min it was already in kernel panic upload mode.

I have no tweaks packages installed. As you can see there is not even an init.d folder.

---------- Post added at 11:42 AM ---------- Previous post was at 11:42 AM ----------

Be sure to check apply on boot then hit apply settings
[Samsung Epic 4G Touch] g_ding84:
You have to set it to apply on boot. If you just change it it will set back to default on reboot. In the SS very bottom. :)

I use voltage control for CPU settings tho.
[Samsung Epic 4G Touch] Goddly:
On boot needs to be checked. ;) thanx g. I thought you were at work bro ;)
[Samsung Epic 4G Touch] g_ding84:
I am. Cigarette break. ;)
[Samsung Epic 4G Touch] btvolta:
Backup and restore

I've tried all the Recovery kernels for GB27 and none are working correctly for backup and restore. Yesterday, I made backups of both The Goodness FK23 Rom and Jellyverse v1.0 and they both seemed to backup correctly, but when I restore, it's almost like dirty flashing over each other because the icons from The Goodness were restored into Jellyverse and vice versa. Once the restore was finished , I had to dirty flash the Rom I was restoring in order for it to be correct. Is this happening to others as well?
[Samsung Epic 4G Touch] SelfElevated2:
Yeah.. was a discussion on tbsg IV about something similar. Upon leaving that for jellyverse I had to flash el29 and flash 2x wipe all zip because all the old status bar icons followed the first time. I havent tried any backups yet tho.

Im just glad their is jb 4.1 source now because now wer moving forward:)
[Samsung Epic 4G Touch] btvolta:
Thanks. I'll have to try the 4.1.
[Samsung Epic 4G Touch] jdsingle76:
There are issues with the latest kernels, as several threads have alluded to. I have gotten good backups of JV using Agat's GB27 repack that he built before source dropped. I didn't use it as a daily, only flashed it to do backups/restores, then flashed back to a stock kernel(before the new kernels that is). Good luck! Hope that helps.
[Samsung Epic 4G Touch] btvolta:
Thanks for the response. Yesterday I downloaded the one that was released prior to source, but haven't flashed and tried it yet. I'll try it later.
[Samsung Epic 4G Touch] jdsingle76:
You're welcome. Just know that there are issues with the GB27 repack as well, mainly restoring, dl of apps. That's why I used a stock as the daily. But the repack worked fine for me for backup/restore of JV. Enjoy
[Samsung Epic 4G Touch] garwynn:
While I wait for Agat I'm going to play around with the local clone of his ramdisk.

I suspect some of these issues are fstab related.

However, last time I tried to change it I lost the USB and external SD card storage.

Now that I have my E4GT in hand let me try playing around with it today.
[Samsung Epic 4G Touch] dataman:
garwynn what was the conclusion on Ko's tweak and the governer's

any patches? or removing init.d is the only way? do you know what tweaks I will lose?