yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] KELO777:
GOT A ?

WHAT DOES THIS MEAN -Make a nandroid in your current recovery then proceed IT THREW ME OF DOES IT MEAN TO MAKE A NANDRIOD BACK UP?
[Samsung Epic 4G Touch] spitefulrain:
Since this is based on 5.0.2.6 doesn't that mean it doesn't support backup/restore from internal memory? If so I may have to wait on this one.
[Samsung Epic 4G Touch] albie1937:
Thanks. I have odined the rogue kernal thinking that this was a ROM w/Kernal. I'm good right now.
[Samsung Epic 4G Touch] Steady Hawkin:
That is correct

You are correct. By default nandroids will be written and restored to your external sd card. We will be updating to the newest base on our next release.
[Samsung Epic 4G Touch] ptfdmedic:
Here you go. This is flashable via CW....
[Samsung Epic 4G Touch] ptfdmedic:
Thanks and you quite welcome ;)
[Samsung Epic 4G Touch] paranoid android85:
Nice. Just odind. Seems good so far. Glad you threw in interactive gov.
[Samsung Epic 4G Touch] LoveisPeace2012:
Yes indeed development is picking up swiftly!
[Samsung Epic 4G Touch] HondaCop:
Let me be the first just for ****s and giggles... How's the battery life? *runs for cover from flame throwers* lol

- My name is HondaCop and I am a troll.
[Samsung Epic 4G Touch] ptfdmedic:
Holy mother of God. I just hit over 5000 on Quadrant. :-)
[Samsung Epic 4G Touch] corybucher:
Can some post the commands to do this on the phone using a terminal app?
[Samsung Epic 4G Touch] gerald410:
Great Job Steady! will be flashing on my Touch shortly.
[Samsung Epic 4G Touch] asteetva:
su and bb essential to install prior to flashing?

If I flash this on unrooted phone and then install any of the rooted roms that include su and busy box, will it work or I have to install rooted rom first so that I have su and bb and then only flash this?
[Samsung Epic 4G Touch] kiekan:
Just flashed this. WOW. Over 5k in Quadrant! Thats nuts! Thanks Steady Hawkin!
[Samsung Epic 4G Touch] maddoggin:
yes!!! thank you sir. i love what you did to recovery very simple and to the point. hated the new functions in cwm 5.0.2.7 thank u!!!
[Samsung Epic 4G Touch] tomyboombotz:
Ptf is that just kernel?
[Samsung Epic 4G Touch] VECTUS:
I'VE FOUND A NEW LOVE... Dont tell my wife!
[Samsung Epic 4G Touch] tomyboombotz:
Anyone just have the kernel to flash
[Samsung Epic 4G Touch] jaysmi32:
What are your overclocking settings?
[Samsung Epic 4G Touch] nyflyguy:
Can this kernel be used on an odexed rom?
[Samsung Epic 4G Touch] JohnCorleone:
Be careful running any video or games at 1704. Those will push your phone. I have been told that in order to test true stability, you set min and Max to 1704, DONT CHECK SET ON BOOT, then run Quadrant at least 4 or 5 times and maybe a few Smartbench runs as well. If you don't freeze then you are probably ok to use it as a setting. Good luck. Hope you can get it stable! You can also try slightly increasing the voltage
[Samsung Epic 4G Touch] Biker1:
I hear ya.

Low on battery. Charging up, and will try later on.

Prior to currently charging, I set min/max to 1704, surfed a few minutes, then freeze. Couldn't get a Quadrant to complete without freezing.

OV to 1500mV but that was a pretty quick freeze on Quadrant test.

Noticed battery at 38% which most likely contributed to the above issues.

Will try again later.

Gotta get some shuteye :-)

1400-1600 is sufficiently Fast enough for me, as well is 1200.

But wanna play with 1704 to see if I can get it more stable ;-)
[Samsung Epic 4G Touch] ewalk4866:
Thats what it was telling me to but it should be all fine just down loaf it and flash in cwm that where the truth came out that it was 1.1.3 just try it and see for your self
[Samsung Epic 4G Touch] thatdudepoops:
Any plans on voodoo support? This kernel is beast great work hawkin
[Samsung Epic 4G Touch] JBNAquatics:
Fellas, if you want to have it stable enough to run quadrant then up the mv to 1525. However, it will not pass cfbench. I ran quadrant 5 times with no issues.
[Samsung Epic 4G Touch] tandxcstar1:
Love it!! oc and stable at 1.7 conservative. 1500Mv. I must have a good device... No freezes yet our locks!! Awesome
[Samsung Epic 4G Touch] Biker1:
Just ran your settings for a minute :

- device froze

- upon reboot, battery level dropped from 46% prior to 12%

I had my SE4GT running for 10 minutes prior at 1700, until I tried Quadrant, then it froze.

Also ran prior at 1700, but froze after a few minutes of surfing
[Samsung Epic 4G Touch] sader2202:
Anyone who overclock above 1.4 ghz if crazy. My device was never the same after I overclock to 1.6 ghz and run quadrant standard. Now to avoid lag I have set the freq to 500 to 1.2 ghz and have the voltage the same on all freq. Sigh to bad I have sprint, getting a replacement isn't going to be easy like it was for T-mobile.
[Samsung Epic 4G Touch] Biker1:
I have various profiles on setCPU, of which 1504 is the max.

I was under the impression that the CPU is able to tolerate speeds above the intended 1200MHz. If not, everyone who OC'd would be burning out processors. At least that is what my impression is.
[Samsung Epic 4G Touch] lafester:
I can't get to 1600 no matter what I do. I got 1504 stable by upping the voltage so at least thats something!
[Samsung Epic 4G Touch] greatlakesghost:
Mine runs at 1704 no issues so i guess I am one of the lucky ones. Dialed it down though just in case. Great work steady hawking!
[Samsung Epic 4G Touch] cordell12:
Is anybody experiencing any choppiness? I am running calks rom (latest) and at any frequency and or governor my launcher (go) and games are choppy, almost like its skipping frames. I tried upping voltages by 25 and got the same results. Also using SetCPU rather than the scripts for CPU control on the rom. The first version didn't give me any trouble, I can flash back to it or Lost kernel and all is well again.

Thanks
[Samsung Epic 4G Touch] thatdudepoops:
ChoppyNess? I'm running Pandora and typing this and its disgusting how smooth it runs... CPU set at 200-500 max lmao etc good job yo on this kernel

Edit: now that I think about it, can u pit in some low frequencies like 100, 300, 400, 500, 600?. Try straight drippingas low as I can go and see how far I get lol
[Samsung Epic 4G Touch] Steady Hawkin:
Thanks for the support! We will continue to support this and our stock kernel, however were are going to somewhat shift our focus to making a kernel to support ICS. I have gotten a taste of it, and im hooked :D
[Samsung Epic 4G Touch] thatdudepoops:
Any chance one the voodoo and low frequencies r Is that moving on to the next project...
[Samsung Epic 4G Touch] yokken:
chiming in to say that i flashed 1.1.1 and it gave me some signal problems, like a text kept failing to send even though i had service. when i rebooted, i got a text that hadn't come through yet, and was able to send my other text out. so it's like i got LoS but it wasn't fixed.

went back to old rom/kernel. flashed 1.1.3 and it's alright for now, we'll see how battery life and LoS work out. pushed it to 1704 for giggles/benchmarks, man seeing 5300 in quadrant really blows my mind. did a multithreaded linpack, it froze right after i did the second test, before it delivered a result. so, no overclock for me. i don't really need it, it's plenty fast. i just like the interactive governor.

p.s.

you should add smartass
[Samsung Epic 4G Touch] JohnCorleone:
ICS is really nice. Best of luck on the kernel.
[Samsung Epic 4G Touch] xlGmanlx:
couldn't agree with this more. My opinion, which in essence means nothing, is that this move is the most important for the community. Short term pains, long term gains as this kernel will be the cornerstone of our phones being truly exposed for the straight beasts that they are running ICS.
[Samsung Epic 4G Touch] kcstier:
LOS with this Kernal

Experiencing LOS 3 times so far with this kernal? Any fixes in the works or alternatives?
[Samsung Epic 4G Touch] fordmanck:
Try the pulled stock version.

Sent from my SPH-D710
[Samsung Epic 4G Touch] Biker1:
I experienced 2 LoS's.

Don't know if it's kernel related, but I've had the least LoS's with what I have tried out in my Sig, and have checked.

I also set up 4 CPU profiles in setCPU.

Phone runs nice and smooth, with very nice battery life.
[Samsung Epic 4G Touch] Rob4828:
What volts did you set it at? Did you benchmark???
[Samsung Epic 4G Touch] greatlakesghost:
I up my volts by 50 being that is what caulmin reduced them by in his rom and ran multiple benchmarks, 6 or 7 linpak and 3 each of quadrant and smartbench. Which I know they mean nothing but was just playing and seeing what I had to work with for later builds :-)
[Samsung Epic 4G Touch] spitefulrain:
Just decided to check, and i can run 1.7 on performance with no problem at all. Even ran some benchmarks, and flew right through them without a stutter. Great kernel, hardly any LoS.
[Samsung Epic 4G Touch] xlGmanlx:
Calk also has a zip that lets you go back to the stock voltage also just a FYI
[Samsung Epic 4G Touch] greatlakesghost:
Ya I didn't even think of that at the time, was too excited and apprehensive both lol thanks for the reminder though :-)
[Samsung Epic 4G Touch] Dchibro:
So, there is definitely something about this kernel that cuts "suspend" and "events/0" system processes (part of Android OS) dramatically. Both were at about 2 seconds CPU time yesterday after about 12 hours off the charger. I flashed to the Rogue Stock kernel last night (didn't want to chance LOS on my road trip to NorCal), and today, both are at about 15 seconds after only 4 hours off the charger.

I don't know what it is about your kernel build SH, but the difference is very noticeable.
[Samsung Epic 4G Touch] chunology:
This kernel is sexually sexual and does sexual things to my phone - should be renamed to Sexual Kernel.

Overclocking? +1

Underclocking? +1

Undervolting? +1

AOS bug gone?!?! +10000000

Coupled this with Calk's 1.5a (comes standard) and the dreaded AOS bug is GONE!! If Calk's ROM is the vagina, this kernel is the secretion that makes everything wet, wild and much more enjoyable. Thank you very much Team Rogue. Very much looking forward to your work on ICS.
[Samsung Epic 4G Touch] redram38:
Forgive my stupidity but what is AOS. I know about LOS and have gotten it several times with this ROM and even after I switched to the newest stock kernel. But am unfamiliar with AOS.
[Samsung Epic 4G Touch] greatlakesghost:
Pretty sure that was a typo
[Samsung Epic 4G Touch] JBNAquatics:
It's not a typo, he really did mean AOS: android operating system bug where the AOS is high in the battery usage. This kernel really does keep the AOS as low as possible.
[Samsung Epic 4G Touch] chunology:
AOS bug is the Android OS bug. Pretty much, it prevents the phone from going into deep sleep and drains the battery.

It is explained in detail here

^This :)
[Samsung Epic 4G Touch] redram38:
Thanks have been given. Thank you
[Samsung Epic 4G Touch] greatlakesghost:
oh my bad, duh. Sorry. I too have suffered from that before this. Sorry, been long day.
[Samsung Epic 4G Touch] xak944:
I flashed this last night, and it seems that it "fixes" the Android OS bug by preventing the CPU from entering 'deep sleep' state altogether. Is this true?
[Samsung Epic 4G Touch] odub303:
No. I have no deep sleep issues with this kernel.
[Samsung Epic 4G Touch] mike19722:
Thanks

works great and battery life is awesome

Michael
[Samsung Epic 4G Touch] dtr145r:
any chance for hid support in your kernel??

wiimote controller doesnt work....

thanks for your work. im running your stock kernel now.
[Samsung Epic 4G Touch] cordell12:
^^^ Quoting myself here ^^^

Having had to revert back to LoS kernel due to the choppiness I was getting I kept pondering the issue I was having. I would re-flash this kernel and get the same results, Chop Sui. Finally boredom over came me while searching for something to flash. I downloaded this kernel again, loaded it up on my SD, went into recovery and flashed the newly downloaded zip. Took a few to 1st boot due to dalvik rebuilding, once on home screen I went to SetCPU changed Governor to Interactive and havent looked back! My guess was I had a bad download or something IDK. Whatever it was it is gone, lol. I should have done this way back when I was the only one with the coppy issue :o

Thanks!
[Samsung Epic 4G Touch] >MR.T:
Sorry if its been answered, I did scan through the 42 pages, and searched. How do we adjust GPU ?Thanks for Res Ponce.
[Samsung Epic 4G Touch] xak944:
Okay, my issue seemed to resolve itself after a reboot, now entering deep sleep correctly. It's only been one day, but so far no LOS, good performance, and best battery life yet! Probably due to the fact that the Android OS bug being fixed. I assume based on the battery life that this isn't just masking the issue like some other kernels have done, but rather actually fixed the underlying issue. Looks like this might be my new daily driver.

Thanks very much to the devs!

Some battery screenshots attached.

EDIT: I just realized that I actually wasn't running undervolted today, although I know my device is stable at those voltages in the screenshot on other kernels. I'll run them now and see how they work.
[Samsung Epic 4G Touch] bpditty:
Trying With SB Now

I just flashed this to run with Starburst 1.9.8r with a 800 underclock (interactive) and -50 undervolt. I will let everyone know how it works out but running well so far.
[Samsung Epic 4G Touch] psych2l:
Would also like to know this as well :confused:
[Samsung Epic 4G Touch] daniel4653:
I just did a reboot and my battery dropped from 52% to 19%.. ..
[Samsung Epic 4G Touch] HondaCop:
You need to calibrate your battery every time you change kernels.
[Samsung Epic 4G Touch] odub303:
Sometimes that prevents this kind of thing and other times it doesn't. I find that it happens more often when I use Quick Boot as opposed to rebooting via the power menu. It also happens more often on the first discharge after a rom or kernel flash.
[Samsung Epic 4G Touch] 1mp4c:
Why do all the Kernels for the SGS2 have the recovery built into it? I never saw this on my Evo. Sry for the noob question, new to the sammy :P

I also get Los on this kernel still with Caulkins 1.5a Rom. I'm gunna try the stock kernel repack and see how that runs.
[Samsung Epic 4G Touch] air2k57:
Yea even the original epic was different, by that I mean kernels never replaced recovery. Even though the process is very similar on this phone, somehow every kernel can get you root and recovery. This kernel is neat, but I did get Los on it, bars would still be there nut nothing would work. However, when I flashed stock rom with this kernel, it worked great.
[Samsung Epic 4G Touch] cjwaggsrx8:
Blazer rom...
[Samsung Epic 4G Touch] playya:
check here and the Q&A Section
[Samsung Epic 4G Touch] Entropy512:
No you don't.

https://github.com/Entropy512/linux_kernel_sgh-i777/blob/master/drivers/power/max17042-fuelgauge.c

Read it. Understand it. Note that it has NO provisions for loading battery heuristics into the device. If you are unable to read it, then trust me when I say that there is NO way to calibrate the MAX17042.

However, at low state of charge it does seem to drift a bit, causing it to "glitch" when the chip is reset. I've never seen this myself, but it happens sometimes, just ignore it and top off your battery as I've only seen it happen at low states of charge (below 50%)

Steady Hawkin: Thanks for being one of the better kernel developers with nothing to hide and a clean github commit history. You might want to git-am this patch though:

https://github.com/Entropy512/linux...c9eb85807302583259e27013ed184a43107bb67.patch

It fixes one specific drain scenario that our devices can encounter.

Also, be careful about rebasing to .14 - it provides no conclusive known benefits and masks (but does not fix in ANY way) the infamous "AOS bug", making it harder to diagnose when it happens.

Tonight I'll edit this with a link to the data from controlled tests where .14 made *zero* difference as far as drain.

I do know that netarchy and ninpo tried basing up past .11 on Ninphetamine, but then reverted back to .11 - between .11 and .12 happens to be where AOS behavior changes. I don't know if this is why they reverted or not, they're difficult to reach these days.
[Samsung Epic 4G Touch] Steady Hawkin:
Thanks allot for the info, well be adding that patch in our next release:D
[Samsung Epic 4G Touch] JoeBruin32:
Should I wipe cache/dalvik before flashing the zip to go from 1.1.1 to 1.1.3? Couldn't find answer, hard to search while on phone.
[Samsung Epic 4G Touch] Steady Hawkin:
No, the install script will wipe for you.
[Samsung Epic 4G Touch] Dchibro:
Interesting. So this probably explains why I saw such low suspend and events/0 process usage in BBS? It may have been masking the usage? I did notice other odd battery usage reports on this kernel, like certain user apps like games not showing up on the battery usage list at all, but I didn't run the kernel long enough for anything conclusive. I had to switch to the stock kernel for a Thanksgiving road trip as I knew I'd be driving through low and no service areas and didn't want my cell radio going dead on me. My phone roamed like a madman driving through BFE cental California farmland, but no LOS on the Rogue Stock kernel hehe.
[Samsung Epic 4G Touch] Entropy512:
It is EXTREMELY rare for this to ever be needed when flashing a kernel. In fact the only time I've ever seen any sort of wiping needed when changing kernels is if you use Xan's Voltage Control and change to a kernel with a different undervolting interface. (SetCPU is better in this regard - it detects when the kernel has changed significantly and resets to defaults.)

Yup. 2.6.35.12 causes suspend and events/0 (along with Android OS reported usage) to drop DRASTICALLY while not changing drain at all.

Some more info:

http://xdaforums.com/showpost.php?p=18699641&postcount=345

http://xdaforums.com/showpost.php?p=18761069&postcount=364

There is a fix to cpuidle between .13 and .14 that does help battery usage in some cases, but that specific fix was backported to .7 by codeworkx (it's fairly early in my kernel commits for the I777)
[Samsung Epic 4G Touch] xlGmanlx:
@Steady - Just thought you might know, in the thread about getting the "fix" pushed.....well the "fix" is being pushed to the user's phone right now. Anyone know how to help him pull it out so the Dev's can tear it appart and see if it solves LOS?

LINKY

Here are the details from the thread
[Samsung Epic 4G Touch] JoeBruin32:
*disappointed* I was hoping this would fix my AOS.
[Samsung Epic 4G Touch] 12MaNy:
+151948914591911419
[Samsung Epic 4G Touch] Entropy512:
Based on the description of the problem in that thread, I'd say it's 50% likely to be in the modem, 40% in the RIL, 10% in the kernel. (High chance of modem/RIL combo with no kernel involvement.)

So those blaming custom kernels for LOS might have been experiencing placebo effect. I know I never once saw someone post a logcat or dmesg of the problem the few times I stopped by here, and the one time someone claimed to be working on a "LOS fix" kernel, he threw so much other crap in there that it may as well have been "just another kernel".
[Samsung Epic 4G Touch] Dchibro:
I don't know Entropy. I personally don't think it's a placebo effect. I've seen enough reports from owners, as well as my own personal experience to feel very strongly that it's a kernel issue.
[Samsung Epic 4G Touch] graffix31:
is this kernel going to able to be updated based on the ek02 pull? just wondering now with the new modem if these kernels wont cause los like they did before. running your stock now on caulks rom and love it and the recovery is the best.

thanks for all your work.
[Samsung Epic 4G Touch] Steady Hawkin:
We will continue to have two kernels. One will be a stock pulled with tweaks and our recovery, the other will be source compiled with tweaks and our recovery. The main reason for this is, Sammie has not been good about updating kernel source. However we will continue to implement various patches, commits, and tweaks as they become available. Thanks for your support:D
[Samsung Epic 4G Touch] Entropy512:
Steady, has anyone experimented with determining if the DPRAM drivers in I9100 update3 are an improvement from yours or not?

It looks like Samsung almost completely nuked and repaved them.
[Samsung Epic 4G Touch] kwan:
I'm sorry to report that ek02 modem and this kernel still gives me LOS.

The only time I don't get LOS is if I'm on stock kernel...Before and after the ek02 modem update. So the only variable that makes a difference for me is the kernel.
[Samsung Epic 4G Touch] Dchibro:
Thanks for the info. It's as I would have expected. I'm looking forward to Samsung releasing the kernel source for the EK02 update (or whatever the final release version is) so our great kernel devs like SH and chris can get back to working their magic, hopefully LOS bug free.
[Samsung Epic 4G Touch] Steady Hawkin:
Were looking into that, and a few other things as we speak:D
[Samsung Epic 4G Touch] thatdudepoops:
Will this kernel see voodoo support?
[Samsung Epic 4G Touch] Entropy512:
There is no component of voodoo (Sound, Lagfix, or Color) that is applicable to any Galaxy S II. Different sound chip, different screen, and it's already ext4.
[Samsung Epic 4G Touch] Steady Hawkin:
Pending some testing, we have some good stuff on the way :D
[Samsung Epic 4G Touch] daniel4653:
Sweet! Will the new update be based on ek02?

:)!
[Samsung Epic 4G Touch] chris41g:
no... 10chars
[Samsung Epic 4G Touch] graffix31:
Is there a reason why? Are there really no difference?
[Samsung Epic 4G Touch] thatdudepoops:
I didn't think about that thx. I wanted sound :( great kernel tho.
[Samsung Epic 4G Touch] Steady Hawkin:
Because Samsung has not updated source. Testing thus far on our unreleased kernel has yielded excellent performance and battery improvements. Lots of patches, and a change of strategy. It will be our best kernel yet:D
[Samsung Epic 4G Touch] stangdriverdoug:
We'll I'm running the current version and really like it so far.
[Samsung Epic 4G Touch] Dchibro:
Sounds great! I'm really hoping to see the EK02 source code from Samsung soon though. LOS has me relegated to a stock kernel until it gets figured out. I'll probably try your update though. Running a stock kernel feels so bland and boring lol.
[Samsung Epic 4G Touch] greatlakesghost:
Totally agree. I don't leave home without it lol

my drama free epic touch 4gee
[Samsung Epic 4G Touch] Entropy512:
Probably a difference - it's just not possible because Samsung has not released the source code they used to build EK02 yet.

There's a possibility that I9100 update3 has the same DPRAM driver as EK02 though - I know Steady was looking into that. He hasn't pushed to github in a while so I don't know what he's up to. :)
[Samsung Epic 4G Touch] Bad--Dog:
Is there a reason that only one core is showing active on this kernel in system tuner?
[Samsung Epic 4G Touch] scarmon25:
Just downloaded the app and checked mine and both cores seem to be working. The second core goes offline from time to time but it does seem to mimic the first one when it comes online. So I'm assuming its working as its supposed too. For me at least

.

Sent from a Blazed SGS II