yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Thanks for testing. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
NP :beer: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Ok first off thanks for the work and sharing it with all of us. Also I just want to say you have an awesome attitude here. Your extremely polite, helpful and honest. So thank you for that. Your work is greatly appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
So i'm noticing that doing a bit more graphic intensive things such as gaming tends to keep freelunch a bit higher in the freq range when compared to other governors. Is there anything we can adjust to keep it's freq down unless it absolutely needs it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
950 mV sounds like a good starting point for rev0 phones. If I ever make a fancy installer, I'll include it as an option.

Questions, constructive criticism, and bug reports are always welcome. If something needs improvement, let me know. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
You got it buddy. I was not getting good battery life before, using freelunch and the other recommended settings. Probably more of an issue on my end rather than the kernel but I will be sure to be vocal this time around when I get to flashing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
freelunch isn't working terribly well on 4.3, and as far as I can tell, battery life is even worse than interactive. :( I think it just needs its settings changed a bit, but I haven't looked into it enough to find better defaults.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Freelunch has been working wonders for me :) Been using your kernel for about 2 months now. Almost can't live without it :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
That seems to contradict the 2 posts following it, what gives? :laugh:

Seriously though I'm kinda confused, dev says it's not working well with 4.3 and has worse battery than interactive and users say it's the next best thing since sliced bread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Not all of our devices are identical and therefore react differently to different settings. Probably explains why free lunch works great for some and not so great for others. The same reason how some devices can't handle OC or uV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Flashed the latest test and its running AMAZING!! I'm getting about 1hr of screen time for every 10% of battery. That's pretty damn good compared to cyanogen kernel and the rest!!!!!

amazing job :)

With 45UV and no OC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
45 UV for each voltage? more info?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Yeah -45 across the table.

No OC or anything changed. ROW and on demand with 2048 read ahead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
So it turns out it has nothing to do with 4.3, I just didn't notice when the bug first turned up. :o I used to regularly get 5+ hours of screen time every charge. I haven't been keeping tabs on my battery lately, but it's definitely much worse than it used to be.

Recent builds have a bug that causes freelunch to excessively raise the CPU to the maximum frequency. I fixed that, and discovered that there's also a bug elsewhere that makes freelunch horribly unresponsive now that the other bug is fixed. I'm working on that, and I'll put up new builds once it's sorted out. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'll wait to flash it until that build is pushed....really looking forward to it! I love the idea of freelunch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
You're in luck! I think I finally got the other bug tracked down, and new test builds for 4.3 and TW are on their way.

AOSP 4.3 Changelog:

Bugfixes for freelunch

TW Changelog:

Bugfixes for freelunch

Added color controls to Trickster (20 = trinity colors)

Stripped touchscreen and wifi drivers

Fixed a few miscellaneous bugs and potential bugs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
I downloaded (checked MD5) and attempted to install the TW test version, however, it does not boot. (I wiped cache and davlik cache prior to installing). I also attempted with and without the vmin 950 however, it still wouldn't boot. Is there anything I could have missed or is there a problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I didn't test the TW build, and apparently it's not booting for anyone. I'll look into it tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks, saved my time for restoring the backup. Will hold until the new tw build is up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
New (fixed) TW test builds are on their way up. I actually tested them this time.

Changelog:

Fixed the freeze during boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
Tested; works as expected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks fit the update. Getting reboots even on first boot, reverting to last tw release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
Did you wipe cache and davlik cache first? Are you on a rev0 device?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
What does rev0 device mean? Is it the hardware version the phone uses? Mine says rev0.4 does that make my phone a rev0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Hmm. What happens leading up to the reboots?

It's the processor revision; rev0 was the original process used to make Krait processors. In the early production of Krait processors, Qualcomm was having trouble with their 28nm fabrication process, and some (but certainly not all) of the processors needed extra voltage.

For the purposes of processor voltage, AFAIK rev0.4 isn't rev0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
I noticed in the latest TW test kernel, I did not have to change the voltage as the minimum is set to 850mv. The cracking sound is not present, so the fixes and code cleanup must have resolved it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Rev 0.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JRock80:
My device is a rev0.4 device as well. For optimum performance, I recommend setting the minimum voltage to 950.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Touchwiz version is exceptional. Does anyone else have the problem where Trickster gives inaccurate min and max frequencies? It seems to be only cosmetic because they appear to be cycling, just annoying. I know KT fixed that bug, just seeing how widespread it is.

Nobody makes mistakes here. Everyone is perfect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
It doesn't show up 100% of the time, but everyone has it. As you mentioned, the frequencies do apply, but continue to display incorrectly. There's a bug in some code from Samsung that causes it (I guess they assumed that nobody roots their phone :p), but I haven't gotten around to fixing it. I'm working on TW anyway, so I guess I should actually fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Good news: new TW test builds are on their way, and they should fix the frequency display stuff.

Changelog:

This happened.

Fixed the bug where frequencies show incorrectly. I think.

Finally updated FauxSound to the latest version. I forgot about TW when faux updated it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
Tried the new tw version, and am having some issues. When using the keyboard, I am getting massive lag, and then the phone will freeze. Occasionally it freezes so bad that I have to reboot. Most of the time it will "catch up." When running your stable version, everything is flawless, except for the frequency reporting. New version doesn't seem to be reporting frquency correctly either. Still the best kernel I have run. Battery life is great. Reverting back to the stable version, though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
CM updated the video drivers again. New test builds are going up, and the usual warning for updated video drivers applies: if your ROM hasn't merged in the updated drivers, do not flash this build; wait a couple days for your ROM's next build to come out. Anything built on 10/19 or later should be fine.

Changelog:

Synced up with CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickdoherty:
Did it work ok for you, i had very bad display function after install (only top half of screen and all blury), maybe bad download, just checking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The update well work only with CM build later than 9/19. CM recently introduced some video changes which was included in this release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
10/19* ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Same, I also had to reflash rom and gapps to get baxk to normal...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I'd like to address a few issues related to the most recent TW and 4.3 builds.

The most recent TW build includes a massive update from Linux 3.0.31 to 3.0.100. It exposed a number of bugs, mostly affecting the GPU driver. I am aware of them, and am working on them. In the meantime, I recommend not running the most recent build! The previous build is dramatically more stable.

The only change in the most recent 4.3 build was to support the updated, unstable drivers in the recent nightly builds for a few ROMs. These updated drivers break a few transition animations and cause frequent GPU crashes that require a reboot to fix. No other changes were made in the most recent build, and therefore the only reason why you should update is for compatability with updated ROMs. Please do not request that your ROM devs merge in the updated drivers. Asking your ROM devs to break their ROMs in order to support an otherwise identical kernel build is senseless.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hey op, hope you have read that 4.3 will be released for our devices in the next couple of days.. I am running the latest leak, missing the dkp magic though..
[AT&T, Rogers, Bell, Telus 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.

I haven't seen a Sprint leak to test with yet, and I won't be able to do much until Samsung posts some updated kernel source. Supposedly, Sprint will get an OTA on the 6th, so it shouldn't be too long before I can get started.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
I flashed the last kernel but the display is cripted please help me

Envoyé de mon SGH-I747 en utilisant Tapatalk now Free
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
What's the ROM and build date?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jbl16:
I'm getting the same crypted display.Just updated to CM 10.2 SNAPSHOT M1 and used the stable build kernel for aosp 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
I was getting the same but my issue was the rom date was prior to the kernel date (du rom) once i used a earlier version i was good to go
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidDude24:
Stabilty

Is the 4.2 aosp kernel pretty stable coming from the stock cm kernel? sorry this might not be the place to ask.
[AT&T, Rogers, Bell, Telus 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
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
Will the new AOSP kernel be for 4.4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Maybe. The 4.4 kernel is still pretty similar to 4.3, so it might work for the time being. I'll probably wait until official CM11 builds start before doing a dedicated 4.4 build.
[AT&T, Rogers, Bell, Telus 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
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stanguay:
Work great on my I747M, the only thing I found is the kernel don't keep Max CPU Frequency. I put the max at 1305 and it always going back to 1512. The Min work at 216.

I tried with SetCPU and Tricsker

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeppelinrox:
FYI flashed all at once...

Latest Quantum 3 RC4 (kit kat)

Latest pa gapps

dkp-aosp43-2013-11-21-stable.zip

enable vmin zip

Enabled ART and overclocked to 1836mhz

Overclock settings/voltages stick when applied with boot script.

...And it's ALL GOOD.

Btw I had ran it over with a 2.5 tonne asphalt roller a couple of weeks ago.

Only damage was the extended life battery (which saved the phone), camera lens (which is the only broken thing - torch even works lol) and severely cracked screen - which is hard to read but works just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Hmm. It looks like something in the kernel changed in the updated source, and the max doesn't apply if it's below 1512. That narrows it down to a tiny bit of code, so it should be pretty easy to fix. I'll get a fixed build out once the festivities are over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Hey, with your i747m and dkp 4.3 tw kernel is data, wifi, gps working fine? Which 4.3 rom are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Oh n decimalman, happy thanksgiving and thanks for the great work. Excellent kernel. Thats 4.1.2, hoping for the same greatness on 4.3 kudos my man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
The 4.3 touchwiz version needs an insecure boot.img in order to work properly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stanguay:
Everything works for me, wifi, data, gps !

Rom : Telus stock - I747MVLUEMK5 (flash without the bootloader with Mobile Odin)

Bootloader: I747MVDMF1

Radio, both works: I747MVDMF1 and the last one I747MVLUEMK5

Root and TWRP installed

Hope this can help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
What happens when you flash the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
It doesn't want to boot up. It gets to the lock screen and freezes. Goes into an infinite boot loop. I checked my post.init scripts, everything to see what would cause it. I honestly don't think the max frequency sticks during the powering on process. Which can be a problem for a lot of phones because mine cannot run at a 2.1Ghz frequency during boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
I guess I will skip it until another version is released.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
I was running this yesterday and didn't have any problem. Booted fine, very smooth, and pretty good battery life. Changed to a different 4.3 TW ROM today, but will be trying it again later tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Just couple of hours, things look solid. Quick question : The kernel is based on the official or leaked version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Does the vmin zip help at all? If not, any logs you can send me would be appreciated.

Side note: I wrote the voltage and frequency code in dkp to avoid the compatibility problems other kernels have had at the time. It guarantees that the kernel can't set a frequency above 1512 MHz until the maximum frequency has been manually increased, e.g. by a tuner app. If the vmin zip has been flashed, it also guarantees that the processor will get the same voltage that the stock kernel gives it (which interferes with undervolting, so it's not the default).

EDIT: Don't listen to me. There was a bug that was causing the minimum frequency to be initialized at 54 MHz instead of 384. A new build is coming soon that fixes it.

It's based on official MK3 (Sprint's official 4.3 release) sources.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Another round of TW 4.3 test builds is on its way. There's a lot of bugs fixed, and I'd recommend everyone update. I enabled SELinux, but I'm open to the idea of disabling it again since it can be troublesome. If you flash over a kernel that boots in permissive mode, it'll carry over.

Changelog:

Re-enabled SELinux

Fixed frequencies not changing correctly

Fixed several bugs in the thermal throttling code

Fixed a few shortcomings in the hotplug management code

Fixed CPU initialization code not using the correct frequency

In the near future, I'll port most of these fixes to the 4.1kernel as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Strange, flashing the update cleared by Apps and Data. Hope OP releases the fix, until then avoid flashing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I'm so glad I force redo my backups to externel storage before I go into recovery mode...

I would have lost my angry birds score
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
****...I read this too late! Suuuxxx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
What is strange that it removed system app also. Even Play store was removed after the update :(, now flashed AOSP ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
That's bad. Really, really bad. As soon as I get a chance, I'm going to take down the new build.

I'll look into it tonight. Apparently, the new build only works for me, and the bugs people are getting depend on which variant they have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheddleson:
I've been running the 4.3 odexed ROM from loserskater with this kernel and haven't had any of those issues. The only problem I have is the phone freezes when I try to lower the minimum frequency. Anything below 384 results in my having to force a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Yea the 11/28 build works fine for me...It was just the 12/01 build that wiped all those apps. Im back on the 11/28 test build and its doing fine so far. Just wish I had an LTE toggle on this StockMod Rom, then I'd be set. Thank you Decimalman for you're dedication to making these kernels though for Touchwiz. Their isnt much else to choose from at the moment for 4.3 TW on my S3. No hard feelings. I was just a little shocked at the moment. I've broke way more than that just with my own tinkering ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
After setting up the kernel and doing a factory reset, everything seems good. KSM however, lags my animation transitions. Had to disable it because it was keeping my phone awake all night off the charger.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
I've got a new build in the works. I reduced USKM's default aggressiveness, and the difference was immediately noticeable. Did disabling UKSM help with deep sleep? On the build I'm playing with now, it looks like somehow the deep sleep states are getting completely disabled.

EDIT: Nevermind. I broke everything trying to shut mpdecision up. Oops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
I was going to mention something about mp decision lol. Disabling ksm made my phone sleep like a beauty. Are you going to completely remove it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
Nice. I'll have to look into why UKSM isn't backing off during standby. The reduced aggressiveness should (hopefully) help, but it sounds like it's not handling standby like it should.

mpdencision drives me crazy. I keep it enabled because I think it does a better job than _thalamus' or showp's in-kernel alternatives, but it's seriously temperamental.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DexedrineXR:
Could you disable ksm by default? For some odd reason my phone will turn it back on while in use.
[AT&T, Rogers, Bell, Telus 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: Sorry DexedrineXR, I didn't notice your request until after the builds were done. Give me a few minutes and I'll put together a build with UKSM disabled by default. Hopefully it'll help.

EDIT 2: I think I found a way to fix the missing apps. I'll get a test build together tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stanguay:
The new built is good (12-02). the frequency is fix but I tried to Under volt and it freeze.(need to reboot)

Now it is stable and good Deep Sleep

Thanks for you great work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] decimalman:
[MENTION=5291228]DexedrineXR[/MENTION]: dkp-tw43-no-uksm.zip

If UKSM is still turning itself back on, let me know.