[G2 Android Development] GalaticStryder:
Don't do that, you really need the new security updates in latest releases. Instead, help with debugging this issue by firing a logcat/dmesg/last_kmsg.

I've just tested it right here, working flawlessly on Arch Linux.

Here's the Q&A:

[B][COLOR="Red"]Read this twice before posting![/COLOR][/B]

Q. Is this kernel compatible with LG stock firmware/ROM?
A. No, it's based on CyanogenMod sources and targets only CM/CAF based firmware/ROM.

Q. What are variants on the LG G2 development scheme?
A. As many crap carriers on the market, LG is known to implement region based hardware, this causes the existence of series of devices that are identical but have some differences in terms of hardware. This forces developers to adapt and recreate the device trees for every single model.

Q. How to install this kernel?
A. Download the version you'd like to use and flash using a custom recovery like TWRP. Be sure to use a bump-ready bootstack for your variant. You should know all this once you're here.

Q. I have an error in red when flashing the zip file, what is that?
A. Maybe your download was corrupted somehow, try to download once again.

Q. I flashed your Kernel and it doesn't pass the bootlogo, what to do?
A. Unfortunately, there's no precise answer to your question. It will depend on many factors like firmware/ROM, mods, type of flashing... What I can say is that you should always keep as clean as possible in this environment, use certified firmware/ROM, bootstack... To avoid any trouble, the recommend installation order is: clean flash firmware/rom + gapps on the first wave of flashing, reboot and setup the system as you wish. Go back to recovery and dirty flash the kernel, reboot. This procedure is known to work better than flashing everything in a row cause it allows the first boot to use the predefined configuration for the device and avoids script racing.

Q. I have a "device not supported, aborting..". error in TWRP, what is wrong?
A. Your firmware/ROM's build.prop property 'ro.product.device' may have been modified and doesn't match the device filter protection implemented in TWRP. Ask your firmware/ROM's developer why he did this or post the value for 'ro.product.device' entry.

Q. Everything went fine here but I noticed the kernel is performing too fast by default, I'd like to change that. How to do it?
A. I ship the kernel fully overclocked up to 2.8GHz and most values set to be performance friendly ones. By far it doesn't match everyone else's setup and that's why you must change the main values to match your own usage. Download Synapse to get started on it.

[U][B]Q. I noticed the Synapse UI is so old-school, why can't I use Kernel Adiutor?
A. You can, but that would waste all the time I spent making UKM (read in details) unique for this kernel. You won't be able to use all the guts properly either. So, please don't use Adiutor as main Kernel Tweaking app, you can use it as a fallback option to see the frequencies and etc.[/B][/U]

Q. I noticed that second post is going to have tweaking hints, is that true or mirage?
A. It's true but it will depend on mostly in the discussion we drive in this thread. I try to make everything clear in Synapse UI for everyone to understand and tweak safe.

Q. Why SELinux is set to permissive?
A. Some mods request the usage of permissive policies to work properly, it was needed to please everyone who had the mods before flashing the Kernel. You can always turn SELinux to enforcing in Synapse UI.

Q. I noticed there's no sound control anymore, how to get the bass of my dreams?
A. Sound Control core is more than deprecated and its official app is pay-to-use. Use Viper4Android to play around with audio enhancements, this one works out-of-the-box: ViperAtmos. Just flash MusicFX Installer and AudioFX remover + The version of Viper you'd like, I use ViPERAtmos 5.5 Sony Beats Edition.

It's old and I didn't edit most information yet but it what it is... still can be used to get some basic information about how stuff works here. I also need to put flash instructions there too and highlight this even more.

Voltage settings are not to be changed at all time they way you think, the engineers that produced this phone knew what voltage/frequency the CPU could handle taking many variables into the count. If you wanna lower them, do this with caution, -5 ~ -10.