Im already glad that we were able to make u reproduce the cursor problem
. I usually install the busybox installer from market and update it every time i fresh install a rom, no matter what device is. I will not do it again, but im glad i found out this quite soon, before installing more stuff.
Let me be straight on that.... Superuser is added to firmware by default becaue I like to have it, I can replace system files without reinstalling rom etc. I think it is usefull.
But installing something what compromises system stability etc is not smart and for sure not a good idea if you don't know what exactly installed app will do. About chainfire 3d also, I didn't know what it is, but read it on the market. Using something that is actually graphics driver wrapper on platform for which very few developers have sources is just bad idea.
I don't know guys what you are doing, but if you have problems with my rom I will try to fix it (such as netflix for which I don't have access, so basically all I do is in the dark, I have to release fw to get some feedback about it. To be able to even use netflix and debug it I would need to pay don't know how much for decent VPN account on some US server which will give me US ip address + netflix account).
I fixed ac3/dts, eac3 or dd+ is hardware limitation of built-in amlogic audio decoder as far as I know. Eac3 works fine on M3 platform.
If you have problems with my fw, don't use it or report it (fully - what is installed on device, how that happened...). If error is occurred because of using apps which changes/replaces or whatever system files, that bug reports I will just ignore.
And yes, on older fw, you did not have black screen when replacing busybox because on older fw set_display_mode.sh and reset_display_mode.sh scripts are not using busybox to read/set ubootenv variables.