[Omni Q&A] Entropy512:
Since there are a lot of questions that get asked repeatedly, I'm going to start up a FAQ thread.

Q: Why doesn't multiwindow work?

A: Multiwindow is still a work in progress. It's 90% working but that last 10% (such as the fact that it breaks Google+ layout) is proving to be much more difficult to polish than expected, and everyone who was working on it has been very busy keeping on top of community contributions and core project work. Progress can be followed at https://gerrit.omnirom.org/#/c/1510/ - Please do not comment there unless you are able to build Omni with the patch yourself have a specific suggestion on how to improve the code. (No UI/UX suggestions please, only code - finishing the code is difficult enough as it is.)

Q: Is my device officially supported?

A: Check http://dl.omnirom.org/ - The device support page sometimes is out of date, while the downloads page is ALWAYS current.

Q: Is my device unofficially supported?

A: Check your device's own communities, don't ask in the general omni communities. Sadly, many unofficial maintainers don't communicate with the team at all, or do so very poorly. If your device becomes supported, support is going to come from a maintainer in your device's development community, not from the core Omni project unless you're lucky and have a device that one of the team is interested in for their own personal reasons.

Q: Where do I report bugs?

A: The official bug reporting system is at http://jira.omnirom.org/ - This is only for devices in the list on dl.omnirom.org

Q: Will you support my device?

A: Just like with other projects, for a device to be supported requires that it have a maintainer. We're already short on maintainers and spread a bit thin, so your best bet is to go to your device's own forums here on XDA. Any device support requests posted in the general Omni forums will be reported to the moderators for moving to device-specific forums.

Q: Why don't I have root?

A: We were planning on integrating an opensource version of SuperSU but Chainfire hasn't had the time to finish that up. The rest of us have been pretty busy too. The recommended approach is to install SuperSU from recovery (If you were able to flash Omni, you have a custom recovery capable of flashing SuperSU) and then choose the "Install backup script" option in SuperSU's settings. (The ease of flashing SuperSU is why most of us haven't put too much effort into getting this cleaned up.)

In addition to this, apps which block usage on rooted devices are proliferating, and many corporate policies forbid using a device that is rooted on their network. It's easier for users who need root to flash SuperSU or another solution in recovery than it is to try and remove root. (I realize that as of July 2014, Omni is partially rooted - 'adb root' and 'adb remount' work, we'll be looking into removing this for nightlies eventually in order to allow more users to run Omni when connected to a corporate network.)

Q: What happened to nightlies for jflteatt/jfltexx/other jflte carrier-specific variants?

A: They were replaced by a unified jflte build. jflte supports all individual variants that previously received their own builds. You must manually transition to the new builds by downloading from http://dl.omnirom.org/ before resuming usage of OpenDelta

Q: When will *foo* happen?

A: We do not give ETAs. This is because usually, if we knew exactly what was needed to finish something, we'd likely have already finished it.

Q: Why am I not getting updates for my device with OpenDelta?

A: There are a few possible causes for this. One could be that your device's name changed or it was unified into another device build. (Carrier variants of t0lte and jflte are in this category. Carrier-specific builds such as jflteatt and jfltexx stopped when the unified jflte build started) Another could be that the OpenDelta "update chain" was broken - it happens sometimes. For example anyone stuck on a February 17 build of t0lte or n7100 needs to manually update from dl.omnirom.org

http://dl.omnirom.org/ is always the definitive place to find the latest official build for a device

Q: What are the official IRC channels for Omni?

Development - #omni

Users - #omnirom

Q: I sat in an IRC channel for 30 minutes and got no response, why doesn't anyone talk to me?

A: Many of us are hardcore idlers that never log out even when we leave the house for more than a day. If you ask a question and log out before we return to the keyboard, you won't get an answer. I strongly suggest you learn the Art of the Idler like most of us have. :) It could take a few hours for someone who knows the answer to your question to see it and respond.

Q: I PMed a developer on IRC and got no response, why?

A: See above about us being hardcore idlers. In addition many of us might not see a PM because it's buried way down on our channel list.

In general, unless it ABSOLUTELY has to be private for some reason, you should not be PMing any developer. For one, the Omni team believes in transparency - we want to keep as much discussion in the open as we can. For another, often someone other than the person you PMed could help you.

Also, in general, when pinging people or asking a question, don't ask if you can ask a question - get straight to it. Most of the developers don't like "naked pings" (pings without any real information or question) - see http://blogs.gnome.org/markmc/2014/02/20/naked-pings/ for a great writeup of why.

e.g.

<someuser> ping Entropy512

is not an efficient way to communicate

but

<someuser> ping Entropy512 re: https://gerrit.omnirom.org/#/c/7373/

is MUCH better