[Galaxy S III Android Development] JustArchi:
OmniSwitch is possible to do without digging deep in the sources, unless you want something more than app itself.

The question should be why we should keep Omni instead of CM. When I was moving to Omni, and this was around version 2.3 if I remember correctly, my main reason was the fact that it was constantly improving and had even two device maintainers for i9300.

Since then I was keeping an eye on both CM and Omni. In my honest opinion CM is far more mature, community is improving it over time and even if Cyanogen is a company since some time already, I can't see any negative output on the community.

I like Omni, but I don't like the fact that they started "from scratch" - pure AOSP base instead of starting from mature CyanogenMod base, and improving it. The thing which matters is the support. I don't want to base on AOKP, AOSB, Carbon or even Slim, because simply support and the community around CM (and Omni) is far better and I'm already busy working on both ArchiDroids and ArchiKernel. The thing is, nobody will help me with ArchiKernel, so I want to leave ArchiDroid future in mature, reliable hands - hands of big and awesome community.

CM and Omni is hard to compare, because you can't compare one ROM to another one. Both of them have supporters, otherwise I wouldn't even consider them. So I'll simply say that I like how CyanogenMod evolved over time, the same as I liked Omni back in 2.3 version.

Unfortunately, Omni does not include anything *that* big. I had high hopes and I was pretty sure that I'll see at least one big feature in close future, but unfortunately, nearly all projects are in big WIP status (i.e. MultiWindow, which existed when I was merging Omni, and didn't change much from then). On the other hand, CyanogenMod has STRONG arguments here, including their recent new theme engine, but not only this.

If you want to know how I feel, simply download CM dated december last year and CM from today. Do the same with Omni, and compare progress over time with both of them. This is the main (but not the only one) reason.

Also, like I said before. It's a matter of taste, same as favourite ROM or kernel. You don't need to agree with my point of view, you can simply accept it as my choice if you want. ArchiDroid is still developed mostly for me. I added bunch of useful features and user-friendliness, which is somehow rare these days, but STILL I only include features I like. This is how custom ROMs work, either you accept it or you move along.

Sometimes it may look like I'm not doing anything "special" but trust me that I'm doing a lot. ArchiDroid has one big difference compared to other ROMs. Other ROMs, like temasek, are based on one thing (i.e. CM) and are evolving in framework/android base itself. ArchiDroid is targeting specific device, improvements for this device, tweaks, fixes, optimizations and everything connected with the ROM apart from the base itself. I simply don't have enough time to take care of everything, especially because I'm still a human. Current "big" ArchiDroid feature will be ArchiKernel, previously it was ArchiDroid optimizations. And I dare you, change ROM then say that you don't feel a difference :).

Therefore, I'll repeat the thing I said back in early AD 2.0 times. Don't expect "big" base commits, like i.e. temasek does. Expect further polishing and taking the very best of our device, while still following all base commits and having up-to-date CM :). ArchiDroid targets at being the most i9300 compatible AOSP ROM, this includes fixes, optimizations and tweaks to make it so. It's fast and reliable, if you like CM or pure AOSP, you don't need bunch of features and you like it fast and stable, you'll also like ArchiDroid. If you want a showcase, million of features from which you'll use two or three, and proper bugs related to them, ArchiDroid is not for you.

With ArchiKernel, finally I'm able to reach battery life of ArchiDroid 1.X, and this is the most important thing for me, because kernel is ultra fast and ultra battery friendly. It's still in WIP and has some bugs I'm aware of, but I'm using it regardless of that. In fusion with ArchiDroid ROM, the backend, tweaks, optimizations and so on, it gives me PERFECT combo, the one I wanted back in old 2.0 days. To have AOSP speed and Stock battery life. Now I managed to have both of them, and this is awesome. I don't need Active Display, OmniSwitch, SlimRecents, Knock-on or anything that exists in custom ROMs today. It's not a contest who will steal... ekhm... cherry-pick more. But when it comes to battery and performance, you know who wins this battle :).