[Samsung Galaxy Mini] lorn10:
0) root your phone with CWM (and maybe unlock it also)

1) install TWRP (from CWM or stock recovery) and reboot into it

2) go to Wipe, Advanced Wipe and then wipe both two Cache & System

3) in Advanced Wipe choose Data and select Repair or Change File System

4) go to Change File System and choose EXT4, format it

5) install the Rom --> Note, when finished the phone will automatically restart!

6) boot back into TWRP recovery and install GApps

--> The first boot up takes long!

That's my way and it worked PERFECTLY!:D:D:D:good::good::good:

Now follows my feedback, - [MENTION=5965480]Shadow Of Leaf[/MENTION] I am really overwhelmed! All grave CM11 & Kernel 3.x issues are now resolved. :) This is the CM11 s6500 build we have needed 3 years ago! ;). In this regard, all the other CM11 s6500 developer can learn from you, - even if you are the youngest of them! ;)

In "Flight mode" the battery performance is AWESOME, better then in the CM 10.1 07/07 build. However, when WiFi is enabled, the consumption is clearly higher. Therefore, I decided me to set the WiFi connection in power settings to "never" when the phone enters standby. So this will disconnect the connection. For me that's a good workaround.

I have tested this final build now also with different developer options somewhat deeper. "Android Runtime (ART)" works but doesn't bring any performance benefits, - it slows down the phone. The CPU may be too weak. The often discussed "Force GPU rendering" option has also no positive effects, - this cause more lags when enabled. The GPU may be too weak. ;) However, there is one developer option which I highly recommend to enable, "16bit transparency". Out of mine view, the overall performance is clearly better, smoother more fluid. Near no lags are present!

The only issues which I have observed so far:

- no video and audio playback is on some site possible with stock browser (Tested at the two German website https://www.zdf.de/ and http://www.ard.de)

- when I run a HTML5 test (https://html5test.com/) it repords that no WebGL is avaiable. At the CM 10.1 build it is

Last thing, - the effective type of the NFC controller in our Mini 2 is NXP 44501 aka PN544 C1. Some variants like the GT-I9100P of the Samsung Galaxy S II phone had the same NXP 44501 controller. I ask me now if it is possible to grab the corresponding NXP (KitKat 4.4.4) "blobs" and build with the official NXP-NCI Android stack (https://github.com/NXPNFCLinux/nxp-pn5xx) a compatible driver. I tested the following NFC enabler (for the Galaxy S II) but the CM11 build will not allow me to activate NFC in the system settings. (https://xdaforums.com/galaxy-s2/development-derivatives/mod-nfc-enabler-t1822447/page59)

Little note to [MENTION=7429196]xEmre66[/MENTION], - if you want to check for a compatible CM13 NXP driver stuff then you may look into the source of the Motorola Moto X 1st generation. It has a NXP 44701 which is in fact a PN544 C3. The firmware 1.41 of that NXP NFC controller has also HCE support. ;) However, maybe it (the driver, not HCE) will work for our Mini 2.

In the attachment there are two photos which verify / confirm that I am right with this NXP 44501 matter.