Blog

OmniROM Marshmallow Nightlies Are Underway

Posted by on 4:39 am in android-6.0, Development, Devices, Features, Releases

OmniROM Marshmallow Nightlies Are Underway

With the release of Android Marshmallow (android-6.0) in October 2015, OmniROM has officially begun nightly builds for our supported devices as of January 10th, 2016. The following devices have been included for nightly support: Nexus 5 (hammerhead) Nexus 5X (bullhead) Nexus 6 (shamu) Nexus 7 (2013) (flo) Nexus 10 (manta) The following devices will be added in the next several days: Nexus 4 (mako) Find 7/a OnePlus One As a result of the time gap between the AOSP and Omni Marshmallow releases, along with the now well-known changes in Marshmallow, users will recognize the Settings layout from previous versions of Omni. Many of the features from previous versions of Omni have returned as well: DSPManager with xplodwild’s Stereo Wide Effect Status Bar Network Traffic Indicators Silent Mode (separate from Do Not Disturb mode) Ability to “unlink” notification and ringer volumes Separate Lockscreen Wallpaper OpenDelta OTA System Updater Support for SuperSU in System Settings Along with these previous features come several new and innovative features introduced with the android-6.0 branches of Omni, such as: OmniJAWS (Just Another Weather Service) Weather in Notification Header Long-pressable, custom locations, unit settings, etc. Enhanced Do Not Disturb mode Dark UI toggle With the release of Android Marshmallow, Google also began monthly security releases aimed to address various CVE vulnerabilities. The team’s goal is to have the security patches merged as soon as possible after AOSP source posting. To date, the team has had the merge completed within 24-36 hours after release. A few other minor notes to keep in mind regarding Marshmallow nightlies: OpenDelta only actively supports TWRP recovery for automatically flashing Over-The-Air updates. All other recoveries are unsupported and may not function correctly. Systemless SuperSU is the only current method to root official Android M nightlies Systemless SuperSU must be re-flashed after every OpenDelta update Bug Reports and Feature Requests can be submitted via the Omni Jira Bug and Feature Request Tracker All nightlies are SELinux enforcing Encryption is the user’s choice We will endeavor to keep you posted on new devices receiving Marshmallow support, but in the meantime check out our IRC chat, XDA forum section, and contribute your ideas....

read more

We Have Lift-off! 5.1.1 Lollipop Nightlies Begin!

Posted by on 10:22 pm in android-5.1, Development, Features, General, Releases

We Have Lift-off! 5.1.1 Lollipop Nightlies Begin!

Over the past few months our staff and contributors have been working diligently in order to deliver the best user experience that we can. At this point in time, we have confidence in the stability of our codebase, and as such 5.1.1 nightly releases based on Android Lollipop have begun! This initial roll out includes the following devices: ASUS Transformer Pad (tf300t) ASUS Transformer Pad Infinity (tf700t) Google Nexus 4 (mako) Google Nexus 5 (hammerhead) Google Nexus 6 (shamu) Google Nexus 7 (flo) Google Nexus 10 (manta) Oppo Find 7/7a (find7) Oneplus One (find7op) Sony Xperia Z (yuga) Sony Xperia ZL (odin) If you are the owner of any of these devices, hop on over to our download page and join the party! Please be advised that if you were previously on an unofficial or homemade build, you will need to perform a clean flash/wipe data when moving to nightly builds, or you will end up in a boot loop. As always, we are working hard to expand our device roster, and will roll out nightlies to more devices over time and as we have maintainers to do so. Please refer to our Lollipop status update post for some FAQs, as well as our device status wiki page for the latest updates on device support. Happy...

read more

Gerrit Maintenance

Posted by on 3:05 pm in General

We will shortly be doing some important maintenance on the OmniROM gerrit, in order to support authentication after Google deprecates OpenID in the next week or so. Gerrit should be considered at-risk and out-of-service while we carry out this maintenance. As a reminder, source code can still be accessed from out Github repositories for any Sunday code-fests you had been looking forward to. Apologies in advance for any inconvenience caused – we were held back in waiting for upstream Gerrit to support a usable migration path away from OpenID. We’ll let you know once it’s all working again. (Fingers crossed!)...

read more

Status Update on OmniROM Lollipop

Posted by on 5:08 pm in android-5.0, Development, Features, General

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

Posted by on 12:15 am in android-5.0, Development, Features, General

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: Soon. Help us help you. Long live...

read more

Omni SSL Certificate Expiry

Posted by on 8:19 pm in General

Update: New certificates rolled out successfully. SHA-256 Fingerprint: 17 E9 8E 0B 55 EC B8 44 89 1E AE C0 28 6F 6F ED 3A EE CB 02 0D 70 D7 93 BF B8 A1 B7 A0 D5 28 7E The OmniROM SSL certificate is in the process of being renewed at present. The certificate for Gerrit will currently be showing as expired. We are in the process of renewing it at present. Until then, the following certificate details are valid and correct for Gerrit, which is the main service that will be noticed to have a certificate issue: SHA1 fingerprint: 03:34:61:BF:6E:EE:0C:1B:7E:B9:D9:F7:89:30:03:F2:69:99:E8:5B SHA256 fingerprint: 0E:79:C3:AC:82:4C:64:E6:0D:EA:0E:E5:20:B0:73:C9:C8:35:72:77:B1:B5:E4:78:F9:B7:C7:BE:9B:CF:20:FC It is safe to continue to accept this certificate in your browser for the next day or so while we renew...

read more

Finding Its Way to Nightlies: The Oppo Find 7

Posted by on 1:45 am in android-4.4, Development, Devices

Finding Its Way to Nightlies: The Oppo Find 7

The Find 7 is the spectacular 2014 flagship from Oppo, a Chinese-based company already well-known for their great developer support across the custom Android firmware world. They have opened their arms to the aftermarket firmware projects, like ourselves, even going so far as encouraging its users to try out different ROMs through various posts and polls. To further that development, they provided numerous devices to the OmniROM project and two of our lead developers, Entropy512 and maxwen, began working on the device. The flagship seemed to have almost everything right: A big, beautiful 5.5in screen (1080p for the 7a, 2K for the 7), top-of-the-line specs, a very nice camera, and the gorgeous skyline LED notification light. Unfortunately, for all the good they have done, they did do one thing wrong: the internal storage is set up in the legacy Android fashion, with the /data partition separate from the user-accessible internal storage. This was a great peeve to most users who were accustomed to the unified internal storage solution Google introduced with the Galaxy Nexus and Ice Cream Sandwich 4.0. Oppo, if you’re reading this, please fix this for your next phone! This was also one of the issues that our devs wanted to tackle before officially pushing the Find 7 into nightlies. Now, after a few months of hard work fixing bugs and issues, Entropy512 and maxwen have deemed the device ready for the nightly roster, and have also provided a LVM-based solution that unifies the Find 7’s internal storage, for users who wish to proceed down that route. The nightly builds are now available for download, and are compatible with BOTH unified and non-unified internal storage formats. Please note that this is a unified build that is intended for BOTH the Find 7 and the 7a variant. Happy flashing! And remember to report any bugs you encounter to our JIRA instance. UPDATE: Entropy512 has also put together a very helpful reference for LVM Partition Mapping. We encourage you read it and become familiar with the...

read more

Adding Group Support for External Contact Sync Solutions

Posted by on 12:22 pm in android-4.4, Development, Features

Adding Group Support for External Contact Sync Solutions

We are all familiar with the AOSP contacts app, named People. One of its key features is the ability to create groups and to sort your contacts using said groups. However, this feature was coded in such a way to only work when the user is using a Google or an Exchange account, leaving users who use alternative, external contact sync solutions in the dust. Most of these alternate solutions implement CardDAV, an open protocol implemented by various solutions for use with contact data. Here at Omni, we embrace third-party opensource solutions, being one ourselves. So when community member CRCinAU raised awareness of this issue to Pulser, our team’s friendly security guy and opensource advocate, he promptly uploaded a patch resolving this, and it has been merged after testing. With the patch, all external contact sync solutions may take advantage of groups within the native Omni contacts app without hassle. One FOSS solution DAVdroid promptly tweeted this, showing their support. CRCinAU also wrote an article on the positive news. This feature has already been implemented into our nightly builds, so if you use such a solution, go check it out in the People app! The FOSS community has a place near and dear our hearts, and is of great importance to us. On behalf of all of us here at Omni, we are glad to be able to lend a helping hand to other FOSS projects and encourage others to do the...

read more

Gerrit Temporarily Unavailable [Back now!]

Posted by on 6:23 pm in General

Gerrit Temporarily Unavailable [Back now!]

Update: Gerrit has arisen once more from the ashes! We’ve also updated to Gerrit 2.9 during the time offline. Unfortunately, due to our server hosts’ datacenter not having suitable power redundancy in place we have had an outage on the Omni gerrit instance, which is taking a bit longer to recover from than expected. We’ve got plenty of backups, and we’re working to get it back up soon. Until then, here is a picture of a duckling, to entertain you while we hit the server with a...

read more

Translate All the Things! Omni Moves to Crowdin

Posted by on 12:44 am in Development, General

Translate All the Things! Omni Moves to Crowdin

Localization can make or break the user experience (UX): What good is the feature if the user cannot understand what it does? As such, we view translations as an important matter. Since the start of this project, we have been taking translations on our Gerrit instance, allowing anyone to upload translations for review. However, this has been non-ideal for several reasons: Only the core team have merge rights across all repositories requiring translations, and this adds more work on top of their already very busy schedules; Many people might make for excellent translators, but learning how Gerrit works and uploading patches might be beyond their capabilities; and Translators are currently required to be extremely careful with XML tags and to keep track of what strings had been added/modified/removed since the last time they updated their language, adding a lot of hassle to the job. Due to this, Omni starting looking for a separate system for handling translations. The requirements: One that is more streamlined, easy-to-manage, and puts less strain on our translators. With the suggestion of our community member Michael Bestas (mikeioannina) and his expertise on the matter, Omni has now successfully moved to using Crowdin to handle our translations. Crowdin will allow Omni users to contribute translations far easier than before, and this will lead to higher quality translations than we previously had, improving the UX on various localizations. You will find our Crowdin project here, and if you wish to contribute translations, you may get started by selecting your language and clicking “Join” to become a member of your language’s translation team. Please note that from now on, we will NOT be accepting new translations on Gerrit. All translations must go through...

read more