[Samsung Galaxy Mini] lorn10:
Hey folks!

Here follows now an other (more detailed) feedback regarding my longer testing of the 20170203 jena build.

To say it clear and brief, - my second mini 2 test phone has become in the meantime my primary main phone (at work). :o As mentioned already, the overall working performance is for my usage definitely much better then with bleached's CM 10.1 07/07 build. The biggest advantage of that CM 11 build is the significant growth of the app storage space, - in my case 1788MB versus 920MB (on CM 10.1). :good:

However, to say it also clearly, despite the overall better and faster reactions, - the mini 2 S6500 still remains a low end phone. Therefore, - some things are simply slower. ;) I write this because it seems that there are again and again people out there which want to overclock the mini 2 and hope that they bring it to a much higher level like the "Samsung S7". :laugh: Whatever, maybe the CAF kernel will bring in this regard some last small (but noticeable) performance improvements. I'm really curious about it!

Small list of things which could be better in the CM 11 20170203 jena build:

sometimes, but not every time, there is a slowdown when I enter a phone number. A moment later I can enter it absolutely normally, no lag present, - strange

when the off-powered phone will be connected to a charging cable it automatically powers on and starts up. If it goes then into power sleep, the phone shows (sometimes) a blank "empty" screen. Solution: The phone should stay off when it will be connected to a charging cable

as already mentioned before, the HTML5 video / audio functionality seems to be broken, at least on some sites (http://www.ard.de or http://www.srf.ch/)

the WebGL functionality seems to be inactive, - this may be related to the broken video / audio functionality

The biggest problem is at the moment the instability of TWRP v2.8.5.0. As already reported by user Don Pedro, TWRP has currently a really strange behavior and is sometimes rebooting suddenly during the installation. I wasn't aware of this, now I can confirm it. That was the reason why I haven't installed the latest CM 11 build on my original mini 2 phone.

This bug also affects any upcoming CM 12.x builds so it has to be explored. ;)

An other serious problem have reported several S6500D users who try to installing the CM 11 20170203 jenad build. They failed almost all. I hope to get a S6500D and reproduce this. However, - it may be better to remove the S6500D links until the problem is solved? Otherwise this issue will "produce" more and more frustrated S6500D users.

My last wish regarding any feature CM 11 / 12 build concerns my lovely NFC matter. Why? Simple answer, at my work there is avaiable since several months a RFID capable Keba P30 Wallbox for charging electric cars. It uses primarily MiFare tags, - the support of ISO14443 seems less reliable. So far I understand this matter it should work with any NXP MiFare compliant phone. After registration with the master key, the phone would act as a normal key to enable the charging. :o Well, unfortunately, all NFC capable phones which I have tested aren't working. (Most modern NFC ready phones are missing MiFare capability because they have not a NXP chipset.) Also the mini 2 with bleached's CM 10.1 07/07 build and enabled NFC doesn't work. This is not surprising because the "NFC SmartCard Info" app shows no MiFare support present. (At the CM11 build MiFare support is shown as present but it is inactive.)

Whatever, it would be really really great if someone could try the libpn544_fw.so file of the LG Optimus L5 E610 phone in a future test build and look if this changes something. Until now all my attempts to exchange the libpn544_fw.so files are failed. After reading a ton about the NXP NP544 aka 44501 chipset I know that the correct firmware file is a central element to get it working. The current libpn544_fw.so of the CM 11 package is a wrong one, - it seems to be made for later NP544 revisions.