[Motorola Atrix 2] dtrail1:
I'll post this again with some additions:

NEW BUILD!

This one is great now!

Developed 3 days 'n nights w/o very much sleep - just to finally revert all this work! I reset the state to 2-27 and took only the best out of the last time.

CHANGELOG

- Reset development stat of JBX source to 2014-2-27

- Merge latest CM changes

- Modem driver updated to 3.4 kernel backport

- Implement Kexec Reject Fix for Edison & Targa

- SMP reconfigured, partly backported for CPU timeout & hotplug handling

- Include 3.0.31 Thermal Framework

- CPU scaling fixed by using "original" JBX code (a mix of several backports and custom code)

- IVA Overclock now with 500 Mhz

- Added Intell-Plug & ported to 3.0.x kernel & Dual-Core support

- Added Intelliactive Governor (a fork of the latest Google Interactive Governor)

- Added Nightmare Governor

- Re-Added a bunch of older governors known from older builds)

- HDMI driver updated to 3.4 Kernel backport

- OMAP Video/DSS drivers merged with 3.0.31 additions & keep 3.8 kernel backports

- Added Asynchronous Fsync (Port from HTC) which replaces Dynamic Fsync!

- Power Saving Mode improved (no probing of tasks to single CPU core - just overall power saving! 1. Option in TM -> Specific tab)

RESULT

- FAST performance!

- Battery life is fine again!

- HDMI & Full HD Camera working fine!

- CPU frequency scaling is back!

- Everything is working fine now!

- dmesg Kernel log is clean now!

Some things

New features like Intelli-Plug are included now. What can you do with it? Intelli-Plug is an Open Source replacement for QComm's MPDecisions. It puts hotplug functionality on ALL governors - better saying : it doesn't matter what Governor you use, it will hotplug when it thinks it's good to go for it. Well, I often talked about hotplugging and its benefits - or even its disadvantages. However, all this gives you new abbilites to play around with Trickster Mod and test & find your personal best config.

To give you an example:

Intelli-Plug + Interactive = When watching CPU behavior you'll note CPU1 is going offline - also while screen is ON. So Intelli-Plug recognized that most of current tasks were finished and CPU1 is not needed anymore (for the moment). But it will turn on CPU1 immediately as soon as it's needed, and this process will be not really noted by you - it's going smooth.

Intelli-Plug + Interactive + Power Saving Mode = Same as above, except: You might note that CPU0 behaves different now, that's because Topology (Power Saving Mode feature by name) probes tasks wherever it thinks it's better for power consumption. In my opinion this is NOT the best setting for battery life because it keeps CPU0 more active while CPU1 is offline - just in theory.

Intelli-Plug OFF + Dynamic Interactive ON = Behaviour as usual know from default JBX setting. CPU1 only goes offline when screen turns off. We know that a Dual-Core CPU is meant to be run on TWO cores! All it's architecture is built for using both cores, including it's power management. So it should be less eating power when both cores are active - but saves more power when CPU1 is offline while the device is in deep sleep (CPU1 is mostly not needed now). Disadvantage: When the device is in sleep and any task arrives to be handled, CPU0 has to handle it all alone - this could cause it eating more battery at the end. In example I use Llama to sync up each hour (when in deep sleep), and this must be handled by CPU0 because Dynamic Hotplug keeps CPU1 offline as long as the screen is off. So Intelli-Plug might be a better solution for this. But keep in ming that turning a CPU core ON/OFF also needs power, and when this happens a lot of time it might be not useful for power saving.

Also keep in mind that you can affect behaviour by tuning Governor settings. Whatever, before you're totally confused, just start over trying around and find your best option! :)

NOTE:

I reuploaded the kernel build JBX-Kernel-3.0-Hybrid-Spyder-4.4_2014-03-23.zip!

So just download this one again and watch your device turning ;)

You need to give your device some time to settle after boot! Enjoy