[Sprint  Galaxy Note 4 Original Android Development] ffolkes:
I have been working hard on the latest release! Every time I thought I was done, I had another idea I was excited to implement. One of the biggest changes is a new approach to CPU use. In the past, I have focused on keeping as few cores as possible online, and keeping that core clocked as low as tolerable. After much testing, it appears this is actually not very efficient. It is better to have many cores online, in order to keep scaling as low as possible. This offers much better battery life, and improved performance. However if you have crappy cell reception, your battery will still go fast. Nothing I can do about that. :P

I am reflashing to TouchWiz as I type this, so I can test the new version on that ROM. I should be able to port all the changes within a day or two, so sit tight my TW friends!

If you don't want to reset Synapse, make sure to do the following after flashing the new kernel:

Reset the ZZMoove Scaling tab to defaults. Press the dotted square icon with 4 little squares in it, tap the 3-dot icon, tap "Select all in section", tap the curved arrow icon, then press Apply.

Reset the ZZMoove Hotplug tab to defaults, using the same method as described above, except do it on the hotplug tab.

For AOSP users: On the I/O & RAM tab, scroll down to the UKSM tab and uncheck "Disable UKSM While Suspended" and press Apply.

Plasma 1.16-AOSP for Lollipop 5.1.x (CM 12.1, CMRemix)

Power/Home Doublepress ([MultiButton] tab) - Just like the new Nexus devices! Set to start the camera by default. With the screen off, press the power button twice, you should feel a vibration, and it should start.

ThumbControl - This is the new version of the old "Wide-Press Multi Key" (WPMK). I find it to be very useful, and I plan on doing a video demonstration soon.

ThumbControl elastic mode

PlasmaUnlock more reliable - This fixes a bug egodriver07 found, and should be fixed now.

Periodic laucher/camera/keyboard renice-ing - Experimental, on every 5th home button press, popular launchers, cameras, and keyboards are reniced to hopefully make them stay in memory longer.

ZZMoove: Doublepunch - This is a confusing but very useful new setting. The Native Input Booster (NIB) used to have two levels - one level that was met whenever there was interaction with the display, and the second level which is when interaction first starts, called a punch. This setting adds a third level that can be precisely applied to only certain cores (previously any punch was applied to all cores). The new logic is: persistent relaxed up_threshold for any input, then new input triggers a punch to turn all 4 cores on and raise them to a "ready" frequency of about 600MHz which lasts for a few seconds, while simultaneously applying a doublepunch to 2 cores to bring them to 1,200MHz. This way all the cores can be boosted to a decent (but not too low) frequency, while boosting only one or two cores to a fast speed. Normal scaling will boost the slower cores if needed, but without the lag of having to start from 268 or 300 MHz.

ZZMoove: Swipe booster - The new swipe booster detects swipes and can boost independently of punches. This helps give extra power for scrolling.

ZZMoove: New hotplug settings - Cores are based on core0's frequency, instead of load percentages. All core threshold are greatly relaxed to encourage more cores online.

ZZMoove: Punch/Swipe/S-Pen GPU settings - Control the GPU frequency during these events.

ZZMoove: Punch/Swipe/S-Pen memory settings - Control the memory frequency during these events.

Plasma Fade-in can fade saturation - Not really as exciting as it sounds.

Plasma Fade-in has incomplete fade failsafe - Sometimes the chipset won't cooperate and hangs after only a portion of the fade-in has completed. Previously you had to keep power cycling until it finally went to full brightness. That is no longer needed, as a watchdog is scheduled 1.5 seconds later to make sure the fade-in has completed, and if it hasn't, full brightness will be forced immediately. You will still see it hang, but at least now the situation will correct itself within 1.5 seconds.

Plasma Fade-in bug fixes

S-Pen: More accurate and realistic writing ([S-Pen] tab) - I put a ton of work into this. I recently played around with a Note5 and was impressed with the build of the S-Pen. I have long been annoyed by the Note2/3/4 and the flimsy S-Pen and its wiggling nib. Because of that wiggling, lines would frequently have little barbs when you put the pen down, and little tails when you lifted the pen. After some analysis, I devised a way to try to filter those out via two new settings: [Minimum Trailing Pressure Cutoff Threshold] (set it to 50%) and [Drop First Events] (set it to 2). I will write more about this later.

S-Pen: Touchkey taps now boost like real touchkeys - Taps to the touchkeys with the S-Pen will now boost just like taps to the real touchkeys.

S-Pen: Works with ZZMoove swipe booster - Swipes and flicks with the S-Pen will trigger the swipe booster, if it is enabled.

S-Pen: Events blocked while screen is off - S-Pen events are blocked from Android while the screen is off.

S-Pen: Added adjustable home button block - WorryFree mode doesn't block the home button, but lately I've found myself pressing the home button with my wrist now and then, so I added a block for that.

Experimental: Memory overclocked to 1,200 MHz - Highly experimental, the CPU memory bus has been overclocked to 1,200 MHz (from 1,065 MHz).

UKSM defaults to stay on while suspended - Reenabling UKSM on every resume might have been causing lag at the worst possible time, so now it is just always on.

Custom charging levels now work properly - After doing some testing, I found that custom levels were not being properly applied previously. That has been corrected, and by default A/C chargers will charge at 2,100 mA.

File systems are flushed when home button is pressed

Fixed bug that was allowing input while screen off - Sometimes input was being allowed when the screen was off but the system was not suspended (aka, in a call). This has been fixed.