yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] thedarksavant:
I advise against wiping cache of you are on any of the known roms this won't boot on.
[Samsung Epic 4G Touch] thomas.raines:
Not yet...I'm working on it though...
[Samsung Epic 4G Touch] joefanelli:
Awesome! I can hardly wait for this to be fully compatible with pacman Rom.
[Samsung Epic 4G Touch] MicrosoftBug:
Just wondering if on the next release the recovery could be updated? The version if CWM included is a couple of versions behind.

Sent from my SPH-D710 using Xparent Red Tapatalk 2
[Samsung Epic 4G Touch] joeboo28:
I'm not sure what recovery your using but i use trwp and when I get wicked battery drain I wipe all the normal stuff and the system and then do a fresh install and it usually clears it up
[Samsung Epic 4G Touch] zombiegirl2010:
I've fixed it.
[Samsung Epic 4G Touch] nidpancho:
thedarksavant's kernel for SPH-D710VMUB

I tried the kernel and my Virgin Mobile SPH-D710 got caught in a boot loop. Restored my nandroid backup and tried thedarksavant's kernel. Just booted up into my phone and it seems to be working fine. Thank you for the modded kernel dude!
[Samsung Epic 4G Touch] abadasstanker69:
Which kernel doesn't wipe cache again?

---------- Post added at 01:05 PM ---------- Previous post was at 12:54 PM ----------

Never mind...got it. This should be in the OP IMO.

Anyone got any recommendations on the voltage control? Or is uv still giving the sleep of death?
[Samsung Epic 4G Touch] nidpancho:
thedarksavant's kernel
[Samsung Epic 4G Touch] calisro:
undervolting causes a sleep of death when you don't give the chip enough power for any given step. Its not a kernel issue nor an undervolting issue itself. Just test which steps you can undervolt to what level. Frankly, the gain by undervolting is so little I don't bother. I actually am overvolting my 1600mhz step to make it work 99.9% of the time correctly.
[Samsung Epic 4G Touch] abadasstanker69:
Yeah...thought so. I'm not gonna mess with it. I'm pretty happy on Pegasus with 1.2 I always take a hit in battery life when overclocked. Thanks for the input!
[Samsung Epic 4G Touch] kchannel9:
I thought that too, but then I bumped it to 1.6ghz with a +.25 voltage increase only at 1.6, and I'm getting similar battery life still and the phone is so much faster now, I could never go back to 1.2 :D

sent from my GS2/ET4G (AOKP/CM Rootbox 3.9.1 20130613) on Xparent Tapatalk2
[Samsung Epic 4G Touch] calisro:
I agree. :thumbup:
[Samsung Epic 4G Touch] abadasstanker69:
I'll give it a shot then! Thanks for the input!
[Samsung Epic 4G Touch] kchannel9:
I should add that since posting I feel like the phone gets too hot, so I've switched to 1.5ghz also with +.25 voltage bump only at 1.5ghz, still using the hypertnt governor. Still as fast and a lot cooler so far. Ymmv

sent from my GS2/ET4G (AOKP/CM Rootbox 3.9.1 20130613) on Xparent Tapatalk2
[Samsung Epic 4G Touch] beezie42:
Mine only really gets toasty while it is on the charger or using navigation. I made a profile so it downclocks while it's charging and while screen is off. Problem solved. :thumbup:
[Samsung Epic 4G Touch] kchannel9:
I wanna do that too! How'd you go about it?

sent from my GS2/ET4G (AOKP/CM Rootbox 3.9.1 20130613) on Xparent Tapatalk2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I know you can do such a thing with SetCPU (donate version). Maybe Voltage Control donate, too)?
[Samsung Epic 4G Touch] tt281gt:
Can also be done with free version of romtoolbox
[Samsung Epic 4G Touch] beezie42:
I used rom toolbox pro. I'm sure you can use the free version also. Setcpu also works great. I have profiles setup too so as the battery dies it slowly downclocks too. I'm loving it
[Samsung Epic 4G Touch] Master_Ellis:
Help?

I'm running Slim ROM build 6 dated 5/30/2013 and when I flash LZ P4 kernel it breaks the Wifi Tether app that allows me to tether using 4G. Any fixes for this?
[Samsung Epic 4G Touch] abadasstanker69:
I have mine scaling from 25 to 1.2 and it's working great so far. For screen off profiles I was using setcpu but since I haven't decided on a job yet, I haven't really had to use my phone much
[Samsung Epic 4G Touch] zimlokks:
i can't believe our CPU can handle a speed of 25mhz but it does save us battery :) i suggest not to undervolt 25mhz-100mhz since instead of helping it might cause battery drain :P

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] thedarksavant:
And be very careful setting minimum. If you accidentally set max to 100 your in for pain :)
[Samsung Epic 4G Touch] gamepro602:
....Or accidentally setting the powersave gov. On those low frequencys. Learned that the hard way:rolleyes:
[Samsung Epic 4G Touch] MicrosoftBug:
Ouch for both of you!

Sent from my SPH-D710 using Xparent Red Tapatalk 2
[Samsung Epic 4G Touch] gamepro602:
And that's why setcpu has a flashable zip Disabler
[Samsung Epic 4G Touch] thomas.raines:
Get me a log and I'll see if I can fix it...
[Samsung Epic 4G Touch] demetrios3:
thedarksavant's kernel installs and the works. The problem is I like to wipe cache partition dalvik once a week or so just as maintenance but that is impossible with the hacked version, even after it's installed.

Is there an expected update to the original that allows wiping?
[Samsung Epic 4G Touch] zimlokks:
there will be in time, i know he's working on it when he can but there is a walk-around.

just flash the old kernel(the one that comes with your rom) now let it boot up reflash the modified(hacked) update kernel and wahla :3

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] calisro:
wiping dalvik doesn't do much for you if you have the same apps... the only reason its wiped while flashing a new rom is because apps are replaced while android isn't running.. so wiping lets the dex files get created.
[Samsung Epic 4G Touch] zimlokks:
also a init.s script to bind cache/dalvik-cache to data/dalvik-cache would work i think but would fill data with about roughly 70mb's of dex files

Flowed Away From My Samsung E4GT!
[Samsung Epic 4G Touch] thomas.raines:
Bad idea because there is a potential of overloading data resulting is sluggish performance and random reboots...not to mention the low disk space warnings... I know this from experience...lol
[Samsung Epic 4G Touch] Adreaver:
Yes, but it has to do with the dalvik VM building itself fresh, not the dex files. Otherwise you wouldn't see "Optimizing Apps" on any deodexed ROMs.

Unless I misunderstood and we are talking about two different things.

Sent from my T999L on PACman
[Samsung Epic 4G Touch] calisro:
no your right. I was just saying that wiping dalvik as part of a maintence weekly isn't really that helpful... when upgrading of course....
[Samsung Epic 4G Touch] Non Sequitur:
I flashed the zip from my sdcard, and it's been stuck at the Cyanogenmod boot screen for a really long time. Definitely longer than normal. I'm running one of the newer builds of Cyanogenmod 10.1.

What should I do?
[Samsung Epic 4G Touch] eaponte23:
Read a few pages back and try the link with the modded kernel that doesn't wipe cache.
[Samsung Epic 4G Touch] Non Sequitur:
Is it this post?

http://xdaforums.com/showpost.php?p=43719049&postcount=381

If so, do I just boot into recovery and flash that? Or do I have to wipe anything or flash anything else beforehand?
[Samsung Epic 4G Touch] :
Just flash.
[Samsung Epic 4G Touch] Non Sequitur:
Bootlooping again.

What should I do?
[Samsung Epic 4G Touch] :
Did you wipe cache?
[Samsung Epic 4G Touch] Non Sequitur:
Nope. I just flashed, like you said.
[Samsung Epic 4G Touch] :
That's rather odd. Who's CM10.1 are you one?
[Samsung Epic 4G Touch] Non Sequitur:
Wild for the night. Pretty recent one, either the most recent one or the one before that.

I'm fairly certain it's a build with the new kernel.
[Samsung Epic 4G Touch] calisro:
flash rom.

let it boot.

reboot recovery

flash lz hacked kernel (no wipe one)
[Samsung Epic 4G Touch] Non Sequitur:
I'm flashing PACman ROM for fun now, if I want to use the LZ kernel on that, is it the same process?
[Samsung Epic 4G Touch] Teknician:
Did you restore, at least your boot and system from your advanced restore or restore your complete backup first before you flashed? I just went thru the same thing and the modified version works great.
[Samsung Epic 4G Touch] LucentBirch:
Anyone know why p.4 would cause my icons and text to look blurry and fuzzy with a slight blue tint? P.2 looks fine, but at p.4 the aforementioned problems arise.

thanks
[Samsung Epic 4G Touch] Non Sequitur:
I didn't make a backup because I'm stupid.

I want to clean flash PACman ROM, anyway. One question though, after I install PACman ROM and the gapps package, can I flash lz over that since it's CM10.1? And do I use the modified version?

Also, LucentBirch, go to settings > advanced > Screen > Scenario > CyanogenMOD and see if that fixes it.
[Samsung Epic 4G Touch] LucentBirch:
well, I'm on ReVolt and "CyanogenMOD isn't an option :P
[Samsung Epic 4G Touch] eigokyoukan:
You can flash the modified lz kernel only on pacman right now. And after you flash do not clear your cache as it will bootloop. Other than that you will be good to go. Just keep a nandroid before flashing ;)

The blue/pixely icons are a cm issue and that is the right way to fix. Slightly different name and location per ROM, but same option to change. I have no idea why CM defaults to that ugly blue tint lol
[Samsung Epic 4G Touch] LucentBirch:
okay, thanks!!
[Samsung Epic 4G Touch] Non Sequitur:
Thanks, eigo! I'll do it now. :D

This is an awesome community.
[Samsung Epic 4G Touch] calisro:
yep
[Samsung Epic 4G Touch] LucentBirch:
What would you guys say is the best app for controlling stuff with the kernel. I know voltage control lite is on my phone, don't know if from this kernel or my rom :P, but I was curious if there's anything better/more convenient/easier stuff like that. What's your opinion?
[Samsung Epic 4G Touch] :
ROM Toolbox Pro, SetCPU
[Samsung Epic 4G Touch] beezie42:
Second, rom toolbox pro works awesome for this kernel. Profiles, voltage control, and under/overclocking.
[Samsung Epic 4G Touch] LucentBirch:
Another question, sorry. Is there any reason why my android os has 27 minutes of cpu usage time I've never had the CPU time be higher than my wake time...should it be like this? I'm not actually sure what CPU time they're referring to, just being honest...
[Samsung Epic 4G Touch] deaver_92:
How long after a reboot?

The issue should have been fixed with the last two wftn builds. Although I have been seeing higher than normal Android OS usage and battery drain as well on the most recent wftn. I am using EO's tweaks though so I was going to run a clean flash for a while to rule that and anything else out before coming to a conclusion.
[Samsung Epic 4G Touch] LucentBirch:
Okay what is a wftn build?

To answer your other question: my phone was last unplugged nine and a half hours ago. I don't know when I rebooted last...

It also seems to drain super fast on WiFi...blech :P
[Samsung Epic 4G Touch] deaver_92:
Wild For The Night. It's Dastin's rom. Most other 4.2.2 E4GT builds pull from his report.
[Samsung Epic 4G Touch] LucentBirch:
Well I'm using the p.4 kernel with ReVolt.
[Samsung Epic 4G Touch] deaver_92:
If something is amiss with wftn then it will be the same for the rest unless the dev of that particular rom hunted down and fixed that particular issue on a build pulled from a specific report date. The fix, however, will be overwritten after each sync of the report unless the report has the fix. This is all assuming the dev keeps up to date with the report.

That being said, I have yet to conduct my investigation as to wether or not wftn is the actually culprit.

The more you know...
[Samsung Epic 4G Touch] LucentBirch:
Okay, thanks deaver
[Samsung Epic 4G Touch] LucentBirch:
Will Trickster MOD work with this kernel as well? I know that some apps don't work as well with some kernels as others...
[Samsung Epic 4G Touch] eigokyoukan:
Tested that app out, looks to be working fine for me! Might actually become my default oc/UV app :D
[Samsung Epic 4G Touch] svicenty:
Can I use this cm10. 2. 4.3
[Samsung Epic 4G Touch] thedarksavant:
IMHO Hood Pope is still pretty alpha, so most folks are staying as close to stock as they can. This allows them to find issues and be sure it's the ROM and not some extra or tweak.

The best advice is to just try it. If it boot loops, reflash the ROM to get the default kernel and you should be OK.

You can also try my kernel zip that does not format cache but installs the kernel, though then you can never format cache or you'll bootloop :(
[Samsung Epic 4G Touch] LucentBirch:
Cool! I'm still having my CPU use time for p.4 crazy high after reboot and a full day use almost but it doesn't seem to be affecting battery. Would a better battery stats dump do anything for the dev to see what's happening or no?
[Samsung Epic 4G Touch] tvm2487:
I'm having some trouble getting this amazing kernel to work on dastins cm10.1 nightly build I flash his build and boot once then reboot to recovery and flash the kernel and it just boot loops at the boot animation and won't go any further I let the phone sit there for a half hour last night and still nothing, any ideas?
[Samsung Epic 4G Touch] beezie42:
You need to use the modified kernel that doesn't wipe cache.
[Samsung Epic 4G Touch] tvm2487:
Oh really that makes sense is there a link to the modified one or can I just modify it myself?
[Samsung Epic 4G Touch] deaver_92:
There you are. It was buried in the forum. Might be good to add it to the op.

Sent from my SPH-D710
[Samsung Epic 4G Touch] Dudebowski:
I'm using dastin's official nightlies with lightning zap and exit only's recently compatible tweaks. Used cpu tweak to set it for battery life use, seems to work as advertised.

Must install/boot nightly

Reboot recovery, install/boot LZp4-no-wipe

Reboot recovery, install/boot EO tweaks

Otherwise results in boot loop or half baked tweaks install.

sent from the mobile thing
[Samsung Epic 4G Touch] LucentBirch:
Because my android os is always really high I got watchdog to see specifically what was working on idle and whatever kworker is they were all active while on idle...can anyone enlighten me?
[Samsung Epic 4G Touch] eigokyoukan:
From a quick search:

"kworker" is a placeholder process for kernel worker threads, which perform most of the actual processing for the kernel, especially in cases where there are interrupts, timers, I/O, etc. These typically correspond to the vast majority of any allocated "system" time to running processes.

Basically, its the system and other tasks running. Generic name for kernel threads. Means apps are running.
[Samsung Epic 4G Touch] thomas.raines:
watchdog invokes kworker. The true way to see what's going on is using adb shell on your computer and type top. This will give you an output of what's running. Also, you can use dmesg and logcat.
[Samsung Epic 4G Touch] kthomson205:
Has anyone noticed the sharpness of their resolution, especially in text, be different with this kernel? Is there a way to adjust? Its not a big deal, LZ is freaking awesome, just wondering.
[Samsung Epic 4G Touch] deaver_92:
Apparently it's a known issue with the smdk4412 kernel. It's being worked on.

Sent from my SPH-D710
[Samsung Epic 4G Touch] thomas.raines:
What do you mean sharpness?
[Samsung Epic 4G Touch] kthomson205:
I guess i should have said smoothness, or crispness. It just seems like fonts have a little rougher edges now. Also, the white backgrounds, like in my browser for instance, have a light blue hue to them now. I have went back to stock, and standard cm kernels, but coming back to lz I get the same result every time. Don't get me wrong man, your kernel is awesome, I just didn't know if I was doing something wrong, or if there was an adjustment to be made with script manager or something.
[Samsung Epic 4G Touch] hakcenter:
I was going to do a pull request to your github, but then I thought... meh

Any reason why the /xbin/zipalign and /etc/init.d/* files are not chmod'd to 755 on git ?
[Samsung Epic 4G Touch] eigokyoukan:
If your talking what I think you are talking about, I thought that was an issue with cm.

Most users fix what your describing by going to advance device settings and changing scenario to 'video'.

Attached screenies.
[Samsung Epic 4G Touch] kthomson205:
I actually just now found the 'no cache wipe' version and everythings back to normal.
[Samsung Epic 4G Touch] eigokyoukan:
Oh cool, good to your worked out. Hmmm... Weird the no cachey wipe version smoothed it out.

What ROM are you on, if you don't mind me asking?
[Samsung Epic 4G Touch] kthomson205:
CM Domination on Epic 4g Touch. What I was talking about is still there, but barely at all. I probly wouldnt have noticed if not for what it was doing earlier. Before it looked like there was a nuclear reactor in my phone, kinda looked cool, but hurt my eyes.
[Samsung Epic 4G Touch] kthomson205:
Just found out something interesting. I just installed a ROM with LZ baked in, and the white screen backgrounds and text/fonts didn't change like we were discussing earlier. Strange. What do you think Mr. Raines?
[Samsung Epic 4G Touch] hakcenter:
Which rom, mine?
[Samsung Epic 4G Touch] kthomson205:
Yep...the gentleman
[Samsung Epic 4G Touch] hakcenter:
my guess would be the flash zip has more in it than what lz does. My only guess. I baked in the kernel from his sources and lz_packages... never bothered to look into the zip flash to see what they are trying to do.
[Samsung Epic 4G Touch] kthomson205:
Ahh...that make sense. I like how it behaves baked in better than the zip. Performance is spot on, but there were some graphic changes the zip was giving me.
[Samsung Epic 4G Touch] ktempleton:
Actually i think it has more to do with the modules and drivers being built with the ROM kernel combination just a guess though
[Samsung Epic 4G Touch] hakcenter:
No, the modules are built from kernel source not the rom. The included modules in the flash may not be from the same kernel compile. However modules are not rom specific they are kernel.
[Samsung Epic 4G Touch] wm388:
Love this kernel; it is a must-have for any AOSP ROM I use. I have a few questions that may have been asked already; just want to hear some opinions.

1) Best cpu settings/governor/io/UV for best battery but manageable use (I think I can take going a little lower, because I have crossbreeder also which makes things zippy).

2) Can somebody explain to be what HypervTNT is like? Is it more for performance? How's the battery life?

Thanks thomas.raines for making this possible. I've been using it since Phase 1 and I just never thought to thank you!
[Samsung Epic 4G Touch] Gazzuk:
Can't say I know what hypervtnt is. From what I have read so far its a hyper gov so I imagine it performs well but may not be the most battery friendly? (I may be wrong)

I mostly use noop/conservative [MENTION=218088]Max[/MENTION] 800mhz

I'm testing waters with noop/smartassv2 @ max 800mhz

And also noop/hypervtnt

I like to have the best of all worlds, but primarily better battery life with a little performance. I guess I'll post my findings as I test.

Update:

smartass its keeping frequencies around 600ish.

Hypvervtnt goes from 200mhz straight to max... I imagine that puts some stress on the processor/battery. (No scaling)

I think I'll stick to noop/conservative. Along with the battery and memory tweaks I think I'll be set. :D
[Samsung Epic 4G Touch] wm388:
I've been using sio forever haha, is noop better? Also, isn't conservative a little too slow?
[Samsung Epic 4G Touch] Gazzuk:
I see a slight difference in UI performance on the latest CM nightly at these settings. I do however scale it up to 1000mhz when I feel I need the extra bang. I'm honestly stuck between smartassv2 (keeps frequencies at an average level) with noop (the most battery friendly, I find it slightly better for battery than sio) set to 1000mhz would be ideal. I'm just a battery hog between mp3s, netflix, youtube, and a few games to kill time. (Castle clash, GTA 3)..the 800mhz comes in handy to keep the power draining a little slower than usual. If 800/conservative is to slow for you try 1000 and if its still to slow for you I'd go with cfq or sio/smartassv2 for more of a balance of battery/performance.

Obviously if you want more performance than battery I'd say cfq/ hypervtnt or Lionheart 1200+mhz. For me leaning more towards performance is just too much of a heat/battery hog. (On this device)

Sio is a mix of noop and deadline its simple but I find it slow for transferring data to and from my PC (mp3s and pic backups). From what I've seen, some might even argue its better than noop.

I like cfq since it keeps the overall processing in balance on multiprocessors.

This is just me. Everyone uses their device in different ways. The best thing I can suggest is learn what each setting does and apply it realisticly to the way you use your device. Good luck!

...And BTW this kernel rocks!
[Samsung Epic 4G Touch] hakcenter:
Cfq has nothing to do with multiprocessors. No scheduler does. It stands for completely fair scheduling go read up on it. Back in the days of disk drives it was important to read things in a more linear fashion and use the cache that way you don't have to wait for the disk to do a full revolution to read some tiny file with little to no priority in the current task.

Noop is the most basic fifo, meaning first in first out.

You could argue about battery life on schedulers and you might have a small iota better battery life on noop depending on your device usage.

However priority and scheduling can mix especially when you take into account read ahead.

There is a specific reason sio was made and why it performs well. If you're transferring a lot of little files noop would be better or you could just lower the read ahead on sio.
[Samsung Epic 4G Touch] thomas.raines:
And this is why I say settings vary on the user and device. No board/processor is exactly 100% the same and everyone uses their device different... I get the best results for battery and performance with cfq and lionheart...
[Samsung Epic 4G Touch] hakcenter:
While I would like to agree to some extent, emmc and cpus are the same to the extent on what they are capable with the voltages that are supplied to them. They either work or they do not work. 1200mhz is 1200mhz right ?

Lionheart jumps to max clock then down clocks if the load lowered, so I would be extremely skeptical that you have any perceived speed increase using cfq over even deadline.

IMHO iops are going to be hurt by cfq, when there is little to no delay in requests. There is no reason to finish every request in a linear fashion and add delay by queuing them inline when you can just do the tasks async.

If you want to see some real speed increases remove the journal on the partitions and downgrade the barrier. It is funny how the linux community strongly suggested ext2 and deadline even noop over cfq when solid state drives comes out. I don't see any reason to argue with them when all the benchmarking I've done across 3 of the same phones suggests to me that noop > deadline > cfq. I use sio because it performs a lot better than deadline, not as good as noop, but noop doesn't handle multi-tasking well at all.

BTW on a side note, are you going to sync upstream on your kernel ?
[Samsung Epic 4G Touch] Zxo0oxz:
Journaling is a bad idea on flash memory anyways, with the whole limited amount of writes. Personally, I'm going to begin experimenting with samsung's f2fs, and see how it performs.
[Samsung Epic 4G Touch] hakcenter:
Don't tell anyone else that, they may disagree with you for some reason.

/system/xbin/busybox tune2fs -o journal_data_writeback /dev/block/mmcblk0p7;
/system/xbin/busybox tune2fs -o journal_data_writeback /dev/block/mmcblk0p12;
/system/xbin/busybox tune2fs -o journal_data_writeback /dev/block/mmcblk0p9;

The only partition I don't remove it from is /data, and I have been honestly considering it for awhile now. But hey **** could eventually at some point go wrong if someone was doing something at 1% battery life right ? :silly:
[Samsung Epic 4G Touch] wm388:
Uh, so is anything being done about the high Android OS usage bug? Things like that must be hard to fix because it's such a weird bug.