Status Update on OmniROM Lollipop

Not too long ago we let you know the progress on rolling out Lollipop on OmniROM, and the positive response was greatly appreciated. We are edging closer to nightlies for Lollipop, and figured now would be a good time to answer some common questions:

Why no more 4.4.x nightlies?

Our goal at OmniROM has always been to balance providing support for legacy OS versions and devices, while also providing the latest and greatest versions of Android for current devices. To balance these two (often) competing priorities, we will continue to provide security and critical bug fixes which can either be backported, or solved through a code fix for previous versions and devices which will no longer receive nightly support.

Where can I find out more information on Lollipop status for my device?

We have setup a page on our wiki which identifies the Device, the Maintainer(s), the Status and any Open Issues on the range of devices currently being worked on for Lollipop. You can find it here.

Why is my device not listed as slated for Lollipop?

We do everything possible to support as many devices as we can. That, however, is not always feasible. Some factors that can keep this from happening:

That last one is an important one. Some of the devices that are not (currently) set to receive Lollipop, but could support it and had 4.4.x on it, is due to there being no one to maintain that device. Anyone can step up in our #omni Freenode channel and volunteer to be the Maintainer, but that "title" requires that you have experience in platform development for that device, you have the ability to do so, and that you have the device.

To point number one and two, a good example would be all Exynos4 devices (except for N80xx) which are considered dropped as of this moment while a new set of maintainers are learning the ropes.

What are requirements for a device to reach "nightly" status?

It's often asked how a device reaches the legendary "nightly" status on OmniROM, and these are the three steps:

  1. Active, well-known, and experienced maintainer
  2. SElinux in enforcing mode
  3. Full-functional recovery build for the device


Hopefully we've answered all of your questions, and if not, please provide comments in the G+ post.