[Galaxy Note 3 Android Development] zacharias.maladroit:
the switch was from (modified) stock > MIUI > temasek first

stock & MIUI are based on Android 4.4.2 - I'm using my phone for security-critical things such as internet/phone banking therefore I need an up-to-date operating system and SE enforcing (instead of SE permissive) configuration with the recent discoveries of security holes - also I don't like the granularity with which you can control privacy settings; using security measures on my desktop linux also a lot, better save than sorry & there was a recent ruling if your account gets abused you are responsible for it, not the bank

switching from stock samsung (TW) to MIUI - not being happy how configuration options are to be found (samsung stock) and that bloaty feeling, X-note was great (especially the amount of options) but configuration and things also didn't work everywhere as anticipated, Omega was the last used & best but it unfortunately still suffered from the weird samsung configuration (I know of the simply config but didn't get used to that) and some occasional hiccups where some function wouldn't work (using an rather early version of that, so could have been meanwhile fixed)

MIUI's video player is superb in terms of graphics quality (upscaling of e.g. 720p or smaller videos to 1080p you can hardly notice worse quality or the difference between those videos), music player is quite ok, on MIUI (TW-based) you have even stock camera and can use Samsung's Music Player but it's also based on 4.4.2 (or the base of TW-ROM; there's AOSP-based one but on french or chinese & behind a forum which requires registration, still waiting for MIUI v6 based on AOSP though)

with MIUI I had some issues with the Archos Video Player & other video players (VLC) and privacy concern (how messages are saved in the MI cloud, it should not be a problem but I kinda felt still not secure how things were communicated via the apps) & some performance problems with browsers and sound stuttering (which shouldn't occur)

temasek offers pretty up-to-date and fixed up CM11 based builds, the kernel is awesome and fixes are coming fast - he clearly has a lot of knowledge how things work, unfortunately I got some FCs, stability and battery issues with it

Almost never having used an AOKP, or purely AOSP-based ROM before in the past (except once tried C-RoM on the N7000 but stability and battery runtime were not very satisfying) I decided to go away from CM11 and try these out

OmniROM (-basd), Dirty Unicorns, C-RoM (Kang), Vendetta ROM were the ones matching my criteria,

Reading Cabooch's post with his experience convinced me to give it a try - and he hasn't promised too much:

it's very stable - no FC's, app crashes, reboots, etc. so far - lots of features and fine-grained tuning of privacy (and other) settings

the reason for switching from lean kernel (it's a very slim, lean & up-to-date kernel) was the subjectively worse sound output from it compared to temasek's kernel and the lack of some features - temasek's EXP kernel might be based on CM's source but doesn't mean that it's unstable since temasek seems to read feedback from testers/users, other devs and the logs thoroughly - and that held true so far, sound is really better and there are more features, also had no crashes,reboots,FC's,etc. so far :p

battery runtime seems a little worse with temasek's kernel but it really depends on the settings (e.g. cpu governors, etc.) you're using and there's still some experimentation to do to find the best settings

since the ROM was just recently flashed and yesterday I (for experimentation) converted over to ART (with Xposed disabled/uninstalled) which should (hopefully) slightly improve battery runtime, it already appears smoother and apps are starting faster, work faster

I can't say that much about battery runtime - except:

# playing videos and music uses way more battery compared to stock(TW)-based ROMs - this also has been the case with the Galaxy S - so samsung is still using some neat battery-saving & energy consumption-reducing techniques which the AOSP-based ROMs don't - I'd really like to know if this also is the case with e.g. the Nexus phones and if this could be changed

# with CM11-based ROMs everything feels very very fragile and prone to FC, crash, etc. - which doesn't necessarily have to be the case but every few weeks or even days with lots of changes it's that way (also been like that on the gt-9000/galaxy s, n7000/note1) - at least with nightlies, mind you there are monthly stable releases

# AOSP/AOKP-based ROMs feel quite stable & the feedback seems to confirm that impression so far, the issue with AOSP-based ROMs is that apps seem to have more power keeping wakelocks up and in worst-case scenarios the battery can drain very very fast, Greenify/Wakelock Detector/Better Battery Stats and the wakelock blocker can help here to identify the culprits

# the radio module, RIL and the whole package also seem to consume more battery in idle or usage - at least that's the experience I had on cm11-based ROMs so far; will see how it goes with C-RoM Kang (first impression: some more than stock) and after battery stats have become clearer

performance:

# it's really smooth and fast - no negative experiences so far :)

Hope that helps - this was a rather long post but it should include most of my experience & reasons for switching I got with this phone so far

Cheers