yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
I think I tracked down the issue causing underclocking to get unstable. I've been running a minimum frequency of 54 MHz (at 725 mV!) for a few days now, without any obvious stability problems. Signal around here is awful, so I can't tell whether battery life has improved.

New 4.3 test builds are coming out. Feedback is appreciated, especially if extreme underclocking is unstable.

Changelog:

Underclocking (finally) added

Slightly tweaked freelunch defaults to work better when underclocked. Note that increasing overestimate_khz may prevent freelunch from using your lowest frequency.

Synced with CM, updated to Linux 3.4.67

Updated toolchain. I still haven't put my compiler laboratory back together, so it's still vanilla Linaro.

EDIT: Looks like I forgot to merge in the updated freelunch tunings. Oops.
[Verizon Samsung Galaxy S III] draexo:
I am really confused now as to what kernel to run on what build.... TW.... 4.2.2... 4.3.
[Verizon Samsung Galaxy S III] Mystique:
If you are running a touch wiz rom; use a touch wiz kernel.

If you are running an aosp rom; choose an aosp kernel.

TW, is version 4.1.2 android. I am happily running the latest version of the tw unstable. With the provided voltage, and the amazing free lunch governor.

If you are running aosp, you would have to pick a version of this kernel that matches what you are running.

I stick with tw for the working features.. Having a wife, children and dogs.. No one cares how cool your phone OS is, when you miss something that a working camera would have been able to catch..

Ymmv.

Also assuming that you are on vzw.. MF1 is the latest version of the firmware..
[Verizon Samsung Galaxy S III] draexo:
Seems too many versions of kernels for 4.3 lately. That's what I was getting at.

Sent from my PACmanized S3!! via Tap Talk
[Verizon Samsung Galaxy S III] glman1:
There have been about 6-7 versions since the beginning of September. That's not that much.
[Verizon Samsung Galaxy S III] vmancini3:
[MENTION=4932679]decimalman[/MENTION] Dude, I am shocked about 2 things.....First.... I have no idea what you did (if you did anything) to the powersave governor, but it is super responsive (just like interactive or ondemand even) and of course, like it should, when you're not touching the screen it has the MHz locked at 384 and gets there SUPER fast!:thumbup: Second.... I don't know why I didn't think to try this governor sooner! You've seen my results in the past and I can't wait to see what my battery life is like now! Excellent job dude!:thumbup: Btw, this is on the 9-26 stable build!:)

Sent from my SCH-I535 NOT using that garbage called TapaTalk 4!
[Verizon Samsung Galaxy S III] decimalman:
I haven't touched it. On TW, there's some code that lets the TW frameworks (read: ROM stuff) kick the minimum frequency up when there's likely to be a lot of CPU usage. Otherwise, powersave would just stay at your minimum frequency all the time. If you're mostly seeing 384, 1134, and 1512 MHz getting used, that's probably what's happening.
[Verizon Samsung Galaxy S III] Mystique:
Looks like uksm/ksm is automatically enabled..

Are the lmk values stock as well?

Using an app to check the random entropy..

When the phone boots entropy issue somewhere near 2500.. Then over time (possibly hours not sure..) I will eventually end up with 4096.

I have since stopped using "no frills cpu" and started using Trickster. Keeping with the free lunch governor.

Seeing that the cpu never really gets over 384, I have started not lowering the cpu from the stock 1512 to my usual 1242..

Keeping the cpu this high "seems" to be giving me random reboots where I have never had any problems before. Although it never seems to be used anyway..

I will drop the cpu down to 1242 in Trickster and see what happens..
[Verizon Samsung Galaxy S III] Mystique:
I have removed Trickster (paid version) and gone back to "no frills cpu" and I am not able to make my random reboots happen..
[Verizon Samsung Galaxy S III] vmancini3:
Trickster has never worked well for me...too many things to play with and settings never stick... I say keep it simple....I've been using SetCPU on every phone I've ever had since the OG Droid and it has NEVER failed me!

Sent from my SCH-I535 NOT using that garbage called TapaTalk 4!
[Verizon Samsung Galaxy S III] Mystique:
Loaded 'kernel tuner' which makes init scripts..

my settings for dkp are simple enough that the scripts make the basic changes that I am looking for.

Installed the app, made changes, confirmed the init.d to be correct.. removed all the cpu/kernel/tweaking apps.. rebooted..

Verified settings..

Back to stable phone again..

I now have more than thirty hours running..

I couldn't keep it up more than twelve hours without a random reboot..

Think I found it.. Nothing kernel related at all..
[Verizon Samsung Galaxy S III] skyss07:
I use SetCPU instead of Trickster MOD? Is it okay? BTW, can I know the settings of those who have a great battery life? Well, this is my first time flashing a kernel unlike custom rom.
[Verizon Samsung Galaxy S III] Mystique:
Glad you found the thread.

Battery life is relative to how you use your phone.

I would suggest choosing freelunch as the gov and row as the scheduler.

I would also suggest no fills CPU tuner.

Very simple to use and make changes..
[Verizon Samsung Galaxy S III] skyss07:
Thanks to you man, I don't have No-Frills CPU and but I have SetCPU, are they same when it comes to their actions?
[Verizon Samsung Galaxy S III] Mystique:
Yes I think so.

I think set CPU is paid only..

No frills is free
[Verizon Samsung Galaxy S III] Mystique:
Should frandom() start filled? (4096)

Or is it normal that when booting the device that entropy counts up to 4096?

I can not find that answer..
[Verizon Samsung Galaxy S III] Mystique:
I've just gone back to the stable version..

I keep getting random reboots. Seems to happen when charging is involved.

rm'd the contents of modules and rebuilt dalvik cache..
[Verizon Samsung Galaxy S III] Droid316:
Will the 10_27 testing build version work on eclipse latest Rom? Does the newest test build have the updated video drivers included because I don't think eclipse has his updated to work with the newest kernels from most devs.

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] david_hume:
Basically, if the ROM was compiled after 10/19, then yes, Eclipse works with the 10/27 kernel. Check the change log for Eclipse and then report back.

Checking the website of when it was updated, it seems that Eclipse doesn't have the updated video drivers, so the 10/27 build is a no go unless you want retarded colors. ;)
[Verizon Samsung Galaxy S III] Droid316:
Retarded on these phones is not good. :)

™Sent From My ™SLIMROM™ BUILD 1.8- 4.3.1 Rom Running BMS Kernel With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] EnemasRfun:
Anyone know how the 10/27 experimental build pairs with LiquidSmooth 2.37? I tried it on 2.10 and was getting random reboot (could have been due to the ROM though!).
[Verizon Samsung Galaxy S III] decimalman:
A few people have reported "static" or "crackling" audio on the TW builds. I haven't been able to reproduce this, so if anyone is having issues, a logcat and dmesg would be helpful to track the issue down.

I happened to notice that TW is a month behind AOSP features-wise, so clearly it's time for a new test build. There's also a new (hopefully) stable build for AOSP on its way.

TW Changelog:

Reverted the huge Linux update. I haven't tracked down why it breaks everything, so it's back to 3.0.31 for now.

Enabled underclocking down to 54 MHz

Borrowed a few CAF fixes for major security holes

Updated freelunch to the current AOSP version

AOSP Changelog since last stable build:

Enabled underclocking down to 54 MHz

Added "color temperature" setting in Trickster

Updated freelunch

Linux 3.4.70, updates from CM
[Verizon Samsung Galaxy S III] kinnerful:
IIRC you talked about none of the d2vzw kernels out there implement <384mhz correctly. So now it's been worked out?

Just curious, no offense.
[Verizon Samsung Galaxy S III] decimalman:
No offense taken.

Going by memory, there were a few incorrect UC settings in other kernels at the time. Currently, many other kernels are now doing it correctly. I still have a few misgivings about it, but I think I've fixed the major problems so I don't see a reason not to include it.

I'm still not entirely convinced that UC saves battery. I haven't done any real-world measurements, but my recollection of some synthetic testing was that there's only a trivial difference in power consumption when UCed. I haven't noticed a dramatic change in battery life while testing the UC code, but signal around here is awful, so it's hard to tell.

UC is also notorious for being unstable, especially when paired with UV. Aside from incorrect frequency tables encouraging unsafe UV settings (you'd think after the 3 GHz kernel fiasco, this wouldn't happen, but it still does), the existing code makes a few assumptions that don't hold while UCed, leading to potential instability (I'll save you the gory details). AFAIK, dkp is unique in fixing them, which I'm hoping makes it safe to UC for everyone, and to UV like crazy in the process (I'm running 54 MHz at 700 mV, 150 mV lower than the lowest stock frequency!).

/novel...oops. :p
[Verizon Samsung Galaxy S III] sbattosai:
I have been having issues lately with your kernels decimalman, since October my phone is unstable with dkp, no matter the rom I try. I am also flashing the dkp vmin file, doesn't help. I get reboots, blocked phone and very slow operations. Before October, everything was fine, I used your kernels on aosp and tw roms with great results. Let me know if you want to debug with me (might have to tell me how to do logs...)
[Verizon Samsung Galaxy S III] Mystique:
I would suggest moving/deleting your modules directory.

rm /system/lib/modules/*

Then reflash whatever kernel.

Especially if you are flashing multiple kernels..

Ymmv..

I have 18 hours and 54% left, little over an hour screen time.

One lockup about two hours ago..

Raised the minimum cpu up from 54..;)
[Verizon Samsung Galaxy S III] sbattosai:
I cleaned flash cm 10.2, even erased my internal storage this time. I was on stock for 5 days, flashed the stable dkp and had issues with reboot and then bootloops that a battery pull took care of... But I can try your solution next time.
[Verizon Samsung Galaxy S III] helobubba88:
This happened to me as well. I have since adjusted voltages back to stock using SetCPU and everything seems to be running smoothly for now.
[Verizon Samsung Galaxy S III] decimalman:
Super-duper experimental builds for TW 4.3 are going up. I haven't run into any issues yet, but I've only got everything building an hour ago. Feedback is greatly appreciated, especially since it's Thanksgiving and everyone has more important things to do. :p
[Verizon Samsung Galaxy S III] draexo:
Uh..... Just where would I find a TW 4.3 build for a d2vzw????!!!!! That's exciting stuff!

Sent from my Lovely S3!! via Tap Talk
[Verizon Samsung Galaxy S III] decimalman:
Oops. Sprint finally got a leak and I got a bit excited. Hopefully a VZW leak will be out soon.
[Verizon Samsung Galaxy S III] Mystique:
The TW 11-21 testing build..

Seems to run very high. Keeps reverting back to 1512 no matter what.

Trickster donate and setcpu both can not make the Cpu change.

Update

Seems to be that particular tw rom.. Different rom same kernel works as desired..

Plot twist..

lk and kt of course act the same regardless of the rom..
[Verizon Samsung Galaxy S III] andrew1234abc:
Same

It runs good for a while, even a whole night, but i started using it in the morning (d2usc) 4.3 official and it locked up at 1500 or so refusing to come down, unless max is pushed down. otherwise quite *****in
[Verizon Samsung Galaxy S III] andrew1234abc:
12/01 4.3 d2usc freezes every few min on defaults. Crashes on other govs. Didn't try the patch. Keep up the work I'd help if u say how.
[Verizon Samsung Galaxy S III] decimalman:
I didn't know USC had an official 4.3. I guess I should announce new build here too.

It sounds like the new build is causing problems for almost everyone. :( I'm going to look into it tonight.
[Verizon Samsung Galaxy S III] andrew1234abc:
Your the only person on a d2usc tw 4.3 kernal. Please keep up the good work, I'd do anything to save that last bit of battery. It also fixes a few problems with the unofficial root situation
[Verizon Samsung Galaxy S III] MrWBucket:
I tried the 11-28 build for d2spr. Used it for a bit, seemed ok. I then tried 12-1 and lost over half of my app icons from my app drawer. Rebooted into recovery (TWRP) and it sat at the Samsung screen. I ended up using Odin to re-install TWRP. Then dirty flashed the stock rooted 4.3, wifi fix, and knox removal from cnexus. All the apps were there at that point and things were back to normal.

Not a complaint as I know this was experimental. Just some feedback.

---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------

I tried the 11-28 build for d2spr. Used it for a bit, seemed ok. I then tried 12-1 and lost over half of my app icons from my app drawer. Rebooted into recovery (TWRP) and it sat at the Samsung screen. I ended up using Odin to re-install TWRP. Then dirty flashed the stock rooted 4.3, wifi fix, and knox removal from cnexus. All the apps were there at that point and things were back to normal.

Not a complaint as I know this was experimental. Just some feedback. I appreciate your work on this!
[Verizon Samsung Galaxy S III] decimalman:
TL;DR: There's a new TW 4.3 build up and I'm disabling SELinux.

A few people found that after flashing the 12/1 TW 4.3 build, lots of apps disappeared. I did some experimenting, and discovered that if you have been running with SELinux disabled (permissive mode may even be enough to cause problems), switching to enforcing mode is likely to cause apps to disappear and/or crash. I think I know what's going on, but even if I'm right, it's going to take a few days to put together a fix.

All it takes to convince SELinux to eat your apps is a trivial change in the ramdisk, which means than changing kernels or even ROM versions could cause problems. This is a no-win situation for me: keeping SELinux enabled means that switching to dkp might hide your apps; disabling it means that switching back to another kernel could hide them. For the time being, I've reluctantly decided to disable SELinux. In the future, one of three things will happen:

Someone will put together a flashable fix for apps disappearing and I'll embed it in the dkp zip

I'll bundle dkp with a custom ramdisk (I really don't want to do this), forcing SELinux into permissive mode

Virtually all ROMs will switch to permissive SELinux, making it safe to enable it in dkp

Questions, comments, concerns? Fire away.

With all that out of the way, there's a new TW 4.3 build up. I fixed a bunch of bugs, and this build is noticeably smoother than the previous build.

Changelog:

Disabled SELinux

Fixed (I hope) reboots when underclocking

Fixed frequency boosting not working

Fixed a couple new bugs in the thermal throttling code

Reduced UKSM aggressiveness by default

Disabled some useless or TIMA-related stuff that I missed

EDIT: I think I found a way to fix the missing apps. I'll get a test build together tomorrow.
[Verizon Samsung Galaxy S III] decimalman:
New test build for AOSP 4.4 is going up. Feature-wise, it should be identical to AOSP 4.3, though I did throw in a couple tweaks.
[Verizon Samsung Galaxy S III] andrew1234abc:
On the s3 TW 4.3 Dec 2 build

always appreciate all the work, I figured out the high usage bug which i still have. Its all good tell you start running apps, alot of anything, games. then the cpu is stuck at max on every gov. even at the home screen. clearing all the apps, or doing a task kill saves the processor and returns to normal. noticeable switch so i dont know its a rogue app, just backround usage something

also anything but stock mhz being set to 388 to 15xx something crashes, like if i go to 200 or 1600 within a minuet or two. otherwise this aloud me to install viper4android

always down for nightly!

EDIT: I saw Ridiculous fishing was foreground 10 min, background an hour, and took 30% battery. So its the app not being killed, i don't know if that's the kernels fault or the app, or androids auto app kill timeout.
[Verizon Samsung Galaxy S III] decimalman:
I love getting lots of info like this! :good:

Since it sounds like it's taking a little while before crashing, your processor probably isn't stable with the default voltages at those frequencies. I'd recommend increasing the voltages a little bit. The stock source doesn't have voltages for frequencies below 384 MHz or above 1512 MHz, so I pretty much pulled them out of my backside. ;) I also had to disable a few safety checks in order to get undervolting to work well; if you're using Trickster, turning on "enable minimum voltage" will turn the checks back on.

That sounds like a bug in the app. When it's in the background, it really shouldn't be eating your CPU. It's your ROM's job to kill it, but it's probably waiting until it needs to free up some RAM. Given its popularity, I would have expected Ridiculous Fishing to behave itself.

Nightly builds probably won't ever happen. :( I've had some extra time lately, so I've been doing enough tinkering to get a new build out most days. Unfortunately, I'm just one guy, and I won't be able to keep this up forever.
[Verizon Samsung Galaxy S III] andrew1234abc:
Well glad you do, some devs hate the crit. on the newest everything is the same, lunch runs fine on stock, but anything over or under freezes withing a few sec, even if not hitting it (like i set it to 324 and quickly moved around, still froze at 1100 mhz so it wasnt even on that clock yet. i bumped up the volts 100 for the same with no luck.

When you said stuff about trickster. did you want the enable minimum voltage on or off? you said you disabled them, then turning them on info. I dont know whats prefered.

I'll reload my 4.1 rom and get the kernals MV tables but I remember them being about the same. hmmm. thanks again
[Verizon Samsung Galaxy S III] decimalman:
I don't like having bugs in my work, so if you're having a problem, I want to fix it.

Interesting. 100 mV would be more than enough to stabilize it, and the voltage tables should be the same as they were on 4.1. Turning "Override minimum voltage" on often helps stabilize things.

There's a lot of new code in the last couple builds, and it's possible that there's a bug in it somewhere. After freezing, does your phone automatically reboot itself after a couple seconds?
[Verizon Samsung Galaxy S III] decimalman:
It's time for another TW 4.3 test build. There aren't many dramatic changes, but I did fix a few bugs. Probably the biggest change is a fix for the disappearing apps phenomenon, which means that it's safe to turn SELinux back on.

Changelog:

Fixed the disappearing apps bug

Enabled SELinux again

Added several TCP congestion control algorithms

Fixed a silly mistake that broke several motions

Cleaned some code up, removed a few useless drivers

Compiled with a shiny new toolchain
[Verizon Samsung Galaxy S III] andrew1234abc:
Hi there again, dirty flashed dec 5 and instantly crash over and over on stock...thats wierd? so i went back to backup, and just flashed it again later today (did clearing both times) and it flashed the same, but no crashing what so ever. cool. So trying the MHZ adjustments and the voltages ive managed to get it down to 270-1566 no crash with your table.

Im gonna get thoes numbers right now and post em in a few, but im not sure what causes the odd flash, or the fact that this morning 270 crashed me but now it doesnt. same nandroid backup. i just am watching set cpu and poking at the numbers all i can

EDIT:

this is what I use super stable all speeds

http://teamuscellular.com/Forum/top...ernel-jellybean-imoseyon-droidroidz-usc-v321/

Fast CPU:

Khz(CPU speed), kV(voltage)

192000,825000

384000,850000

486000,875000

594000,900000

702000,925000

810000,975000

918000,1000000

1026000,1025000

1134000,1075000

1242000,1100000

1350000,1125000

1458000,1137500

1512000,1150000

1620000,1200000

1720000,1250000

1809000,1250000

1900000,1300000

This is for a fast processer, but mine tested fast, year old revision B, so a little higher might be in order,

EDIT 2: what TCP u recommend, theirs so many now and wikipeida really makes no judgement
[Verizon Samsung Galaxy S III] andrew1234abc:
Freelunch freezes at any change from stock. Ondemand is clockable over, hmmmm
[Verizon Samsung Galaxy S III] andrew1234abc:
Heres a supprise

So i got freeluch working with some MV tweaking, dont know what it was or what I was missing before, i tested these for 4 or 5 hours and probally reset close to 60, 70 times. So heres the MV I worked out. I use freelunch, and 108-1728. The 54 seems really low and the TW kinda struggles, thus raising the CPU all the time.

I set 1980 to 800. THIS IS INCOREECT. i just didnt need a higher clock speed, was just my personal refrence, just follow my table and estimate for higher speeds.
[Verizon Samsung Galaxy S III] andrew1234abc:
Well back to stock MHz. Its super picky. :confused:
[Verizon Samsung Galaxy S III] decimalman:
There's a new TW 4.3 test build up. It fixes a bug that could potentially crash the display hardware, probably taking everything else with it (thanks, Samsung).

Changelog:

Turned compiler warnings back on (Samsung disabled them :mad:), and fixed the zillions of issues that the compiler warnings were designed to highlight in the first place

Fixed a major bug in the framebuffer driver

Major cleanups to the rotator driver (the name is misleading; it's mostly used for video playback)

Renamed a few devices to hint at what devices they're compatible with

Tidied up a bit, removed a couple unused modules, switched to (smaller, faster) XZ compression
[Verizon Samsung Galaxy S III] beepea206:
I don't see any 4.4 builds here.. http://d-h.st/users/decimalman/?fld_id=29223#files
[Verizon Samsung Galaxy S III] goldsmitht:
uhm, is there a VZW TW 4.3 ROM? haven't seen one yet
[Verizon Samsung Galaxy S III] decimalman:
Nope, but there is a USC TW 4.3 ROM, and they share this thread. In any case, there's a kernel waiting whenever VZW finally green-lights the update.
[Verizon Samsung Galaxy S III] draexo:
I thought a USC ROM would work on VZW?

Sent from my Lovely S3!! via Tap Talk
[Verizon Samsung Galaxy S III] decimalman:
Good news for anyone running AOSP 4.4: new test builds are going up. I haven't spent much time with the code yet, so there isn't a lot of new stuff. Mostly, I got sidetracked and wrote a new novelty. :D If you hate it, you can disable it in /sys/kernel/dkp.

Changelog:

Synced up with CM

Rolled up a handful of changes from TW

Added a fancy gimmick
[Verizon Samsung Galaxy S III] beepea206:
12/13 build doesn't work with gummy 4.4.2 (12/13) build.
[Verizon Samsung Galaxy S III] decimalman:
I've been running Gummy 12/13 since yesterday, and haven't had any issues. What sort of problems are you having?
[Verizon Samsung Galaxy S III] beepea206:
I get a quick reboot to a black screen and the phone freezes. I have to do a battery pull to boot into recovery.
[Verizon Samsung Galaxy S III] thelangosta:
I had this last night while trying to reboot into recovery in order to flash the latest dkp on the 12/13 paranoid android. I also had it once last week on a different rom.

Edit: forget to say that the kernel feels smoother than the previous version did. The only place my phone isn't fully buttered is in the keyboard. It is just a little jagged while swyping. It might just be the stock Google keyboard that is not smooth.

Thanks Decimalman.

Sent from my Transformer TF101