Status Update on OmniROM Lollipop
Feb09

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: Scumbag OEM doesn’t provide their required (or in the case of Samsung, promised) kernel source code OEM has dropped support for their device going forward and their previous drivers are not compatible with Lollipop and beyond There is no one stepping up to become a Maintainer for that device 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: Active, well-known, and experienced maintainer SElinux in enforcing mode Full-functional recovery build for the device   Hopefully we’ve answered all of your questions, and if not, please provide comments in the G+...

Read More
Android L on OmniROM Is Progressing
Nov21

Android L on OmniROM Is Progressing

Having a project which is entirely community-driven and -led is a daunting task, and something we are all so excited to be a part of. It also means we have a variety of questions come in on a daily basis, from “Y U NO SUPPORT [INSERT OBSCURE DEVICE]?” and “How do I flash Gmail?” to “When is L coming out on Omni?” We love interacting with the community, but we also haven’t done a great job of communicating where we’re at with certain things, and that’s something we’ll be working on. We interrupt this broadcast to announce that if you’re interested in helping Omni communicate with the community go Volunteer! To answer the last question about an ETA on when Omni rolls out Android Lollipop, it’s coming soon. The more that our maintainers get done now, the sooner it will happen. Our first priority is getting all of the hardware support stuff cleaned up and ready, and we’ve already seen several devices as old as the Galaxy Nexus (thanks to MWisBest) start to come up and build successfully. In the coming days we hope more maintainers will complete their bring ups and we can progress towards a nightly status. It is also a reality that not all of our currently-supported devices will receive Android L – largely in part to the lack of OEM support for L, but also due to the fact that we just don’t have the maintainers available to support every single device. If we don’t have an active maintainer for a device, then it’s a pretty good chance that the device will not be supported on L going forward. HOWEVER, if you’re interested in becoming part of the Omni project, please let us know and we’ll work to get you involved. One thing which has become abundantly clear with regards to AOSP 5.0 – Google does not care about, or seem to like, AOSP users. They’re breaking the AOSP applications left and right, and pulling many of them back to be proprietary. We’re in the process of getting people together from various projects to fix this. Get in touch if you’re interested – we want to make AOSP awesome again, even without Google apps! One final thing of note is that if you have a device which will not be receiving Android L via OmniROM, we are currently evaluating the feasibility of having a long-term support sub-project working on 4.4.4 if there are enough users with devices that will be left behind. That is another reason to get in touch with us, as if there is enough interest it will help drive the direction. So to sum up:...

Read More