yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] decimalman:
When was your ROM built? The newest commits from CM cause problems on ROMs built more than a day or two ago. CM 10.2 official nightlies are out, and I haven't had any issues (well, kernel issues anyway :p) since flashing it last night.

I'm guessing he merged the same CM commits that I did, but he hasn't updated his git repo in a few days. On recent CM nightiles (official and unofficial) that had the screen tearing, these commits fixed it and everything runs perfectly (for me anyway). On older ROMs that didn't have the screen tearing thing to begin with, the new commits actually cause it.
[Verizon Samsung Galaxy S III] RoboJoe:
notta's Unofficial PA build; built 8/12. He probably just missed it.
[Verizon Samsung Galaxy S III] decimalman:
The commits came out that evening, so he probably missed them. His next build will probably need an updated kernel.

Thanks for the details. It dosen't sound like you've got anything installed that could cause problems.

I took a look through some recent changes, and noticed a change that made sense with the TW drivers but not the AOSP ones. I fixed it and I'll PM you a test build shortly to see if it helps.
[Verizon Samsung Galaxy S III] minnysota:
Thanks for the update. So just to clarify... Flashing your 8/13 test build with Masta's 8/14 nightly should be golden? Or would you advise waiting until you drop an updated test build? Thanks again!
[Verizon Samsung Galaxy S III] 0xScott:
I've been running the version from your PM and it seems to have fixed the problem. So far -- no flicker!
[Verizon Samsung Galaxy S III] decimalman:
Running the 8/13 dkp build on an 8/14 ROM nightly should work fine.

Fantastic! I'm going to upload new 4.2 and 4.3 builds with the fix.
[Verizon Samsung Galaxy S III] decimalman:
Another round of new AOSP builds! I think I've gotten the flickering fixed for everyone now. 4.3 builds are up now, and 4.2 builds will be up shortly.

Reminder: 4.3 ROMs built before 8/13 are only compatible with kernels built before 8/13; 4.3 ROMs built on or after 8/13 are only compatible with kernels built on or after 8/13.
[Verizon Samsung Galaxy S III] dunlap92:
Running slim 4.3 8/10....flashed dkp 8/13 experimental and was getting tearing....seen your post and flashed 8/11 experimental...all good now...Thanks

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] airmaxx23:
The 8/14 AOSP kernel breaks the ringtone and notification sounds on the 8/16 official CM10.2 build.
[Verizon Samsung Galaxy S III] bmeek:
Confirmed with some surprise...

I initially suspected that perhaps you had an A2DP-capable Bluetooth headset connected. There's what I perceive to be an issue where Bluetooth media hijacks ringtones and notifications away from the handset speaker... I've missed many incoming calls after removing my connected headset but not turning it off.

Not sure if this issue is CM-related, an AOSP v4.2+ issue, or is device-specific. It's not a problem on stock TW ROMs (I gather that AOSP got a whole new Bluetooth stack after v4.1).
[Verizon Samsung Galaxy S III] sbattosai:
@ Decimalman: ExFat source code released by Samsung

http://sfconservancy.org/news/2013/aug/16/exfat-samsung/

:thumbup:
[Verizon Samsung Galaxy S III] decimalman:
Thanks for the heads-up. :good: I heard that the exFAT code had leaked, but I didn't expect Samsung to open-source it. It might still take ROM support for exFAT cards to be convenient (meaning TW only for the time being), but I'll add it in and play with it a bit.

EDIT: The notifications thing is strange. There's nothing new in the kernel that would cause it, and I'm getting notification sounds. I'm not sure what I did differently from everyone else, though. :confused:
[Verizon Samsung Galaxy S III] bmeek:
For what it's worth, I never tested notifications. I only verified that the ringtone didn't ring after flashing dkp (and worked fine again after reflashing the latest nightly).
[Verizon Samsung Galaxy S III] decimalman:
Interesting. I figured notifications would be easier to test since it's the middle of the night here, so I didn't test the ringtone.

Also:

New TouchWiz builds! sbattosai pointed out that Samsung open-sourced their exFAT driver, so I decided to throw a new build together.

Changelog:

Finally added Mike Kasick's ram_console and hardboot patches. last_kmsg will actually work now.

exFAT support for 64 GB SD cards. The exFAT driver seems to work on CM10.2, but I haven't tested it thoroughly, and I haven't tested it at all on TW. If you have an exFAT SD card, you should backup any important data before flashing.

The exFAT driver works fine on AOSP as well, but I'm not sure what (if anything) needs to be done to get ROMs to use exFAT SD cards. If anyone has a spare SD card (I don't) and wants to test, PM me.
[Verizon Samsung Galaxy S III] sbattosai:
Thanks man, testing now.

---------- Post added at 11:40 PM ---------- Previous post was at 11:23 PM ----------

Report: kernel bricked my phone. :D

Wait no, everything works great!!

My Samsung micro SD 64gb is working great in Jellybeans 18.

Awesome work Decimalman :thumbup::thumbup:
[Verizon Samsung Galaxy S III] airmaxx23:
Just to add a bit more info, when you go into to sound settings to change the notification of ringtone sound none of them play when you try them.
[Verizon Samsung Galaxy S III] sbattosai:
Can a kernel mess with the gps?

I had amazing gps on stock jellybeans 18 but since I flashed the new TW ExFat kernel, I can't get a lock, no matter what I try... Weird...
[Verizon Samsung Galaxy S III] decimalman:
Curious. Can you grab me a logcat after trying to change the notification? I haven't been able to reproduce the issue yet.

Weird indeed. I haven't made any changes that (as far as I know) would affect GPS, so dkp shouldn't be causing any issues. You're not the first to report bizarre happenings on the new build. I'm going to flash to TW shortly and see what's going on.

On a somewhat related note:

New AOSP builds are on their way. It looks like AOSP 4.3 (and possibly 4.2 as well) should handle exFAT automatically, so if you a) have an exFAT SD card, b) are using the newest test builds of dkp, and c) have made backups of anything important on said exFAT SD card (the driver hasn't gotten a lot of testing yet), you should be able to use your SD card without any headaches.

Changelog:

Added Samsung's GPL'd exFAT driver.

On a side note: I'm not a lawyer, so I'm not terribly familiar with the implications of Microsoft's patents on exFAT. My understanding is that in order for Samsung to redistribute the code under the GPL (which it is), it must be royalty-free for anyone who "receives a copy" (GPL parlance :)), and so it should be okay for us to use. Anyone with a legal background care to comment?
[Verizon Samsung Galaxy S III] airmaxx23:
I can't reproduce it on the 8/17 kernel.
[Verizon Samsung Galaxy S III] bmeek:
Update: after installing the August 17 CM10.2 nightly and your August 17 test build kernel, ringtone and notifications are back...
[Verizon Samsung Galaxy S III] 0xScott:
The 8/18 AOSP build is flickering. I'm reverting back to 8/14.
[Verizon Samsung Galaxy S III] 0xScott:
It's working fine after upgrading to the 10.2 / 4.3 nightly of CyanogenMOD. I had to load the new gapps and lost the old Google Talk that I liked though.
[Verizon Samsung Galaxy S III] jlokos:
Latest kernel working great on carbon 8/18 build and Notta's PA 8/17, including torch, ringtones and notifications. No flickering either. Great job dkp.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
8/18 has Lots of flickering on Rootbox 4.2 after being plugged in for a bit... At one point it flickered until the screen just went black and wouldn't come back on till after a reboot
[Verizon Samsung Galaxy S III] madjokeer:
http://d-h.st/R4N

8.11 more reverted branch has been solid for me.. Battery life and no flicker
[Verizon Samsung Galaxy S III] 0xScott:
Anyone else seeing issues with menu button and back button responsiveness in AOSP 4.3 testing build 8/17? I updated to the latest nightly with the CM kernel and my problems went away. Haptic feedback was working, but the back button wasn't exiting apps. I could long press and kill the app though. I haven't tested enough yet to narrow the problem down to dkp, xprivacy, or any particular setting.
[Verizon Samsung Galaxy S III] bmeek:
I'm running the 8/21 cm10.2 nightly with the 8/17 dkp kernel and am seeing no such problem.
[Verizon Samsung Galaxy S III] soapinmouth:
I'm having this problem but im on latest carbon with ktoon kernel.
[Verizon Samsung Galaxy S III] david_hume:
Only had that issue when I played Candy Crush. Anything else I ran worked without a hitch.

sent from my Carbon 4.3 GS3
[Verizon Samsung Galaxy S III] decimalman:
Unless you need exFAT support, stick with the more-reverts test build. I'll get the flicker sorted out sooner or later.

AFAICT, this is a ROM issue. The buttons seem to be working from the kernel perspective. Also, Android issue 58557 suggests that it's a brand new bug that Google introduced in 4.3.
[Verizon Samsung Galaxy S III] 0xScott:
I'm on the 8/17 build and cm-10.2-20130823-NIGHTLY ROM. I'm not having any problems now with the exception of PeerBlock for the Xposed Framework not working. I'm troubleshooting that now. I switched from Xprivacy back to LBE Security Master. While I'm not a big fan of letting China control my phone's security, I trust them more than Facebook, who explicitly makes me agree to upload my contacts and personal details for marketing purposes.

I saw a flicker or two, but only while changing between screens, and nothing that made me think twice about continuing to use this build as my daily driver.
[Verizon Samsung Galaxy S III] sbattosai:
Hi Decimalman, I tried slim beans beta 3 yesterday and I couldn't see my ExFat SD card with the stock and your 8/17 kernel.

Which 4.3 rom did you use for testing ExFat?

Thanks
[Verizon Samsung Galaxy S III] decimalman:
CM10.2.

I just took a look through CM's vold code, and even with working kernel support, it's still relying on (slow, clunky) userspace exFAT drivers. :( It's possible to manually mount an exFAT SD card using the kernel drivers, but to automatically do it, vold needs to support the kernel drivers.

I doubt that CM (or any other AOSP ROMs, for that matter) will add kernel exFAT support, so exFAT support will most likely always use the userspace drivers on AOSP. If you need exFAT support on AOSP, ask your ROM dev to merge in CM's exFAT support. I'll probably remove kernel support soon, unless I hear about a ROM that actually uses it.
[Verizon Samsung Galaxy S III] sbattosai:
Thanks for the explanation. I don't understand why exfat is not natively merge to aosp now that Samsung has open sourced the code...

So if I understand correctly, using cm 10.2 I should be able to use my SD card using your kernel or do I have to do something complicated myself?
[Verizon Samsung Galaxy S III] decimalman:
You shouldn't even need dkp. It looks like exFAT support doesn't depend on the kernel at all. It should "just work" if you're running CM.

The problem with exFAT isn't actually the source or its license. Like NTFS (and FAT32, to some extent), Microsoft has patents on some components of the filesystem. MS is generally tolerant of open-source software using their patented filesystems, but there's still a concern that integrating exFAT could allow for ugly patent lawsuits.

The Linux kernel is especially conservative when it comes to lawsuits, which is why I doubt that kernel exFAT support will go mainstream. It's possible to support exFAT without kernel support, so that's probably the route that ROMs will take. It's just a matter of getting ROM devs to merge in support manually.
[Verizon Samsung Galaxy S III] sbattosai:
Now I understand 100%

Thanks a lot Decimalman :thumbup:
[Verizon Samsung Galaxy S III] pocii29:
Running 4.3 with no problems. Looking forward to getting my nanolunch back though
[Verizon Samsung Galaxy S III] MisterSprinkles:
Does the 4.2 kernel use Koush's anykernel format?
[Verizon Samsung Galaxy S III] decimalman:
nanolunch was originally supposed to be a quick test to make sure some changes to freelunch didn't cause problems. I didn't get around to merging it back into freelunch until pretty recently. Except the name, freelunch is currently identical to nanolunch.

Mostly. I don't use koush's tools, but I do package the kernel the same way.
[Verizon Samsung Galaxy S III] pocii29:
Roger that I'll move my tweaks to that
[Verizon Samsung Galaxy S III] Jacobz1996:
Kernel

Guys anyone have a link to the kernel want to try it out on quantum see how it works. Anyone try it .
[Verizon Samsung Galaxy S III] Jayydude_SGP:
Anyone else having trouble with OC? I attempted 2.1ghz just to see if it'd work, it didn't. I then started going down one by one and with every selection the phone would freeze to the point of a battery pull is needed. Why can't I OC?
[Verizon Samsung Galaxy S III] Atrizzain:
Not everyone's phone can handle it. No two phones are exactly alike, even if the hardware is exactly the same. My last phone wouldn't undervolt without rebooting, no matter what kernel/ROM combination I tried.
[Verizon Samsung Galaxy S III] decimalman:
Start low and move up. At some point, you'll need to increase the voltages for frequencies that won't run. IIRC, the processor in the S3 was originally intended to run at up to 1300 mV, so that's a reasonable "safe" limit for voltage. If you're feeling daring, dkp will let you raise the voltage as far as 1400 mV.

Also:

New AOSP 4.3 builds are on their way.

Changelog:

Disabled exFAT. It needs ROM support to be useful.

Synced up with CM.

Fixed a stray bug or two.

New toolchain. My compiler laboratory exploded, so it's lightly modified Linaro GCC this time around.

EDIT: Looks like I missed a bug that breaks hotplugging (and also everything) with some governors. I'll get new builds out tomorrow.
[Verizon Samsung Galaxy S III] decimalman:
New, fixed builds on their way.

Changelog:

Fixed a bug where applying certain governors repeatedly could cause major problems.

Improved automatic auto-hotplug. Auto-hotplug will take over if a tuner app breaks mpdecision.
[Verizon Samsung Galaxy S III] vmancini3:
Is there possibly going to be a TW build with freelunch being as quick as it is for AOSP?
[Verizon Samsung Galaxy S III] bmeek:
FYI, the issue with muted ringtone and notification sounds resurfaced for me after flashing the 09/02 dkp kernel and 09/02 cm10.2 nightly. After reflashing the same cm10.2 nightly to get the native kernel back, the ringtone returned.

Would a logcat of the "silent ringing" be of interest?
[Verizon Samsung Galaxy S III] sbattosai:
Nooooo !! We need exfat support! Carbon ROM is compatible and I am using it!
[Verizon Samsung Galaxy S III] decimalman:
You sure? It looks like they're using exfat-fuse instead of in-kernel exFAT. It should still work fine without kernel support. If not, I'll enable it again.
[Verizon Samsung Galaxy S III] bmeek:
Never mind...

I recalled that the last time someone reported the "muted ringtone" issue, and confirmed the same, the issue seemed to resolve itself with a subsequent cm10.2 nightly build (and no kernel updated from decimalman).

On a whim, I tried reflashing the 09/02/2013 dkp test kernel, and the phone rings fine. I swear I wasn't hallucinating, or (not) hearing things... In any case, while this is curious it's not consistently reproducible.
[Verizon Samsung Galaxy S III] decimalman:
That was my impression. I only saw it once, and it disappeared after a reboot. I didn't think to get any logs though. :(

If anyone else runs into the issue, please PM me. I have a hunch about what's causing it, but I need some logs to verify what's going on.
[Verizon Samsung Galaxy S III] bmeek:
Well, before my most recent post, I had powered-down, did a battery-pull, rebooted, and still no ringtone (it did vibrate on ring). If it happens again I'll remember to grab a logcat.

Thanks again for a great kernel...
[Verizon Samsung Galaxy S III] decimalman:
Strange. :confused:

If possible, could you get a dmesg too? It's a little more work, but I think it would help. In a terminal emulator:

su

cd /sdcard

dmesg >dmesg.txt
[Verizon Samsung Galaxy S III] sbattosai:
I don't know if It works or not as flashing the 9/02 kernel corrupted the graphics and blocked the phone in a limbo state where I couldn't do anything (on carbon 9/02). Reboots didn't help flashing another kernel did help.

Sorry I couldn't get a logcat.
[Verizon Samsung Galaxy S III] decimalman:
Yuck. Thanks for letting me know. :thumbup: I'll grab Carbon and see what's going on.

Unfortunately, freelunch is the same on TW and AOSP, which means there's some other factor causing issues. I'm not sure if it just needs to be retuned or if TW behaves so differently that it'll never feel as smooth as it does on AOSP.
[Verizon Samsung Galaxy S III] vmancini3:
Not sure if YOU remember.....? I think it was the first test build you did for TW....what I do know is that it was the one dated 6-16....freelunch was psychotically smooth....that's back when the min and max speeds had a mind of their own regardless of what happened...ring a bell? I still have that build and every other build for that matter...lol

[MENTION=4932679]decimalman[/MENTION] ....just to grab your attention...Lol

Would there be any possible governor adjustments I could make to freelunch? I remember from a PM a while back you suggested to set the highspeed_divisor to 0 (from the default of 6), but unfortunately that didn't really make a difference...
[Verizon Samsung Galaxy S III] decimalman:
I don't remember freelunch being dramatically smoother than it is now, though that's probably just my crummy memory. :o

IIRC I merged nanolunch back into freelunch and made a few changes to related code about that time. I guess I should double-check that I didn't screw anything up.
[Verizon Samsung Galaxy S III] vmancini3:
In the meantime.....somewhere between tonight and tomorrow morning....I think just for the hell of it I'm gonna flash that older build I'm speaking of just to see if I'm the one with the crummy memory:o If freelunch is smoother on that older build then maybe that can be a little helpful towards a perfect, stable build for TW? As it is....I don't think my phone has had a better kernel:thumbup:
[Verizon Samsung Galaxy S III] decimalman:
There's probably some helpful changes that could be made, but I'm not sure what. I'm supposed to be looking into another issue right now, or I'd flash a TW ROM and play around myself.

Let me know. If it's noticeably smoother, there's probably a bug somewhere.
[Verizon Samsung Galaxy S III] vmancini3:
Ok....you got it dude...I know you're busy...I'm probably not gonna be able to flash the older build until tomorrow anyway...
[Verizon Samsung Galaxy S III] vmancini3:
[MENTION=4932679]decimalman[/MENTION]

Just thought you should know....I went ahead and flashed the 6-16 kernel...and boy lemme tell you....it took me not more than 10 seconds to realize that freelunch is definitely quite a bit smoother on this older build....no joke.....definitely noticeable!
[Verizon Samsung Galaxy S III] mickskillz:
I agree
[Verizon Samsung Galaxy S III] decimalman:
New 4.2 stable builds are going up now. After this, I don't plan to continue 4.2 work, since CM isn't updating the 4.2 kernel. Compatibility shouldn't be an issue since there aren't likely to be any further kernel updates from CM, and I don't expect to make any earth-shattering changes in the near future.

Changelog since last stable build:

Fix OC frequencies not sticking.

Fix UV interface for a few apps.

Fixes for automatic auto-hotplug.

A handful of optimizations.

Lots of CM commits.

Merge nanolunch back into freelunch.

Fancy new compiler.

The flicker in recent test builds should be gone. If not, let me know.
[Verizon Samsung Galaxy S III] 0xScott:
Feature request: ignore unstable power detection

I read that this kernel setting might resolve the inconsistent charging results I'm getting with many of my cables. Ones that used to work no longer charge my phone. I only have a few left that I can use.
[Verizon Samsung Galaxy S III] decimalman:
New 4.3 and TW builds! I'm calling both builds stable this time around. TW is long overdue for a stable build, and there (mostly--see changelog) don't seem to be any bugs left. CM hasn't been making dramatic changes to the kernel lately, so I think it's time to call the AOSP 4.3 build stable as well.

Between being out of town for a week and having a few other projects on the back burner, I haven't made many changes lately. The changelogs are pretty short, but new releases were overdue.

TouchWiz:

Reverted some video driver stuff that should fix flickering for those who are seeing it.

Temporarily re-enabled some ugly code that I plan on rewriting sometime soon. It should make everything smoother. Unfortunately, this code causes the bug where minimum frequency shows up incorrectly in tuner apps, so beware.

AOSP 4.3:

Merged lots of CM changes: some CAF stuff, Linux 3.4.60, and a few odds and ends.

I'll take a look.
[Verizon Samsung Galaxy S III] vmancini3:
SWEEEEEET!!!!!!! F'ING AWESOME DECIMALMAN!!!
[Verizon Samsung Galaxy S III] dvaderx:
I'd like to 2nd that request

Thanks!
[Verizon Samsung Galaxy S III] annoyingduck:
4.3...nice :D. Flashing now.

Thanks decimalman
[Verizon Samsung Galaxy S III] tyler.frost92:
Would it be safe to run this kernel with Eclipse 5.1 ROM?
[Verizon Samsung Galaxy S III] saintsantos:
OH HELL YEAH!!! Been waiting on this baby!
[Verizon Samsung Galaxy S III] tvl76:
9/20 stable is running FANTASTIC with Slim rom !!!
[Verizon Samsung Galaxy S III] annoyingduck:
Been awesome on cm10.2 nightlies. Big battery improvement...
[Verizon Samsung Galaxy S III] vmancini3:
Sorry, meant for this to be a reply, not a quote...

New TouchWiz build has been working great!!!!! If I may add....for any other users that might want to overclock just a little....it's been my experience so far, keep in mind, with me having the "fast" processor, that in oder for me to achieve let's say 1728 Ghz, the processor seems to want at least 1200 mV for that speed...otherwise it just reboots immediately!
[Verizon Samsung Galaxy S III] decimalman:
New 4.3 test builds!

Changelog:

Trickster setting to adjust color temperature*, since CM hid the advanced settings screen (which will still work, but is harder to get to than it used to be). The new enable setting doesn't actually do anything, but Trickster won't show the screen without it.

Prevent thermald from overriding OC/UC settings.

Touchscreen driver cleanups.

Synced up with CM.

* The setting in Trickster actually adjusts the intensity of the trinity colors adjustment, similar to how the advanced settings screen used to. 20 = "Cold" = trinity colors, -20 = "Hot".
[Verizon Samsung Galaxy S III] drecu:
Running smooth as silk on the latest nightly with Pac!
[Verizon Samsung Galaxy S III] tracerman:
where did you DL from? the link is down for me

EDIT: Saw the tweet from dev-host

"Dev-Host.org ‏@DevHostOrg 1h

Sorry for the downtime today... resolving an issue with datacenter."
[Verizon Samsung Galaxy S III] tyler.frost92:
Kernel is stable on Eclipse 5.1. Battery life is good with free lunch. Only weird thing is the battery seems to drain faster than normal while actively using the phone, but uses virtually nothing while the screen is off, and the phone is in my pocket. Whereas stock, I would drop percentage a lot faster while the phone was idle
[Verizon Samsung Galaxy S III] drecu:
Ditto on that. Free lunch hardly uses anything on standby but seems to eat it rather quickly while in use especially on a phone call
[Verizon Samsung Galaxy S III] Dearborn1977:
Dev host down for anyone else?
[Verizon Samsung Galaxy S III] tvl76:
^^^^ This for me too.
[Verizon Samsung Galaxy S III] pimpmaneaton:
Yes it is. Not sure how op feels but any one have the latest test care to share.