[Android General] HypoTurtle:
Yea, Light Manager - worked fine on stock AOSP 5.0 - but I can't say that I tried using it to disable all activity from the led - Capacitive Buttons app I can say did/does completely kill the backlight (after toggling selinux/rebooting) - but doesn't with this P7000 Port - something in the system seems to be overriding any third party value writing here (/sys/class/leds/button-backlight/brightness).

Can you run and post the output:

su

grep -R brightness /system

For reference from VIbe2.8:

su
grep -R brightness /system | grep -v app

grep: /system/app/VoiceExtension/lib/arm/libvie_jni.so: No such file or directory
grep: /system/app/webview/lib/arm/libwebviewchromium.so: No such file or directory
grep: /system/app/webview/lib/arm64/libwebviewchromium.so: No such file or directory
grep: /system/app/DeviceTestApp/lib/arm64/libdta_dynamic_load_jni.so: No such file or directory
grep: /system/app/DeviceTestApp/lib/arm64/libdta_mt6605_jni.so: No such file or directory
grep: /system/app/Nfc/lib/arm64/libmtknfc_dynamic_load_jni.so: No such file or directory
grep: /system/app/Nfc/lib/arm64/libnfc_mt6605_jni.so: No such file or directory
Binary file /system/bin/aee_dumpstate matches
Binary file /system/bin/afm_server matches
Binary file /system/bin/atci_service matches
Binary file /system/bin/boot_logo_updater matches
Binary file /system/bin/dumpstate matches
Binary file /system/bin/factory matches
Binary file /system/bin/ipod matches
Binary file /system/bin/kpoc_charger matches
Binary file /system/bin/meta_tst matches
Binary file /system/bin/recovery matches
Binary file /system/bin/testmode matches
Binary file /system/lib/hw/lights.default.so matches
Binary file /system/lib/liba3m.so matches
Binary file /system/lib/libaal.so matches
Binary file /system/lib/libcam.hal3a.v3.so matches
Binary file /system/lib/libcamera_client_mtk.so matches
Binary file /system/lib/libexif.so matches
Binary file /system/lib/libfeatureio.so matches
Binary file /system/lib/libfilterpack_imageproc.so matches
Binary file /system/lib/libvcodecdrv.so matches
Binary file /system/lib/libvoicerecognition.so matches
Binary file /system/lib64/hw/lights.default.so matches
Binary file /system/lib64/liba3m.so matches
Binary file /system/lib64/libaal.so matches
Binary file /system/lib64/libcam.hal3a.v3.so matches
Binary file /system/lib64/libcamera_client_mtk.so matches
Binary file /system/lib64/libexif.so matches
Binary file /system/lib64/libfeatureio.so matches
Binary file /system/lib64/libfilterpack_imageproc.so matches
/system/usr/keylayout/Vendor_05ac_Product_0239.kl:# - Special function keys for brightness control, etc. are not

It could be that just the lights.default.so's are needed from stock AOSP (@goja - I take it the Vibe *.so's didn't work - I thought at the very least they would break the led and make it non-functional - can you try setting the permissions of the lights.default.so files to 000 [---------] just to see if that does anything).

[MENTION=3356343]xenonism[/MENTION] : Someone else might explain better - but for me 2.8 seems to perform better than 2.5 regarding the ROM there are essentially 2 different tracks of VibeUI - there is the ROW versions; multi-language; I think released out of India termed Rest Of the World - this version is currently at 2.5. The Other version is made for local chinese devices - and only built with Chinese(mandarin) and English - with there being some Chinese apps that will be there regardless of language chosen - this version is currently at 2.8 (will need some clarification from [MENTION=6756702]mtllo[/MENTION] (mystory) - it's sort of explained here) - there is a 5.0 and 5.1 version of Vibe2.8 - the one that's available is 5.0 as explained by mtllo ; just fyi. I have booted the 5.1 version but the phone process kept FC'ing and didn't have the time to try and fix it / find a temporary workaround - but if anyone wants to try let me know, and I'll point out the steps to get to where I got.

Regarding CM12.1 - I haven't used it at all so can't say much about it - and it's an unofficial ROM; as I'm fairly sure that not a port but compiled from CM source. But yea it's built independant like the vast majority of CM ROMs and as such isn't maintained by CM so no updates from them.