Blog

New Year, New Month, New Security Updates

Posted by on 7:39 pm in android-7.1, Development, Features, General, Releases

New Year, New Month, New Security Updates

New Updates and Devices With 2017 now upon us, and the collective hangover from 2016 somewhat passed, it’s time to focus on what’s happening this month with OmniROM. As some of you may know, the January 2017 Android Security Bulletin has been released and with it a slew of updates to AOSP. We have merged those into the existing 7.1 codebases (r10) and will be looking to backport soon as well. With a new year comes new supported devices – or at least for this year. Don’t hold us to next January. But for now, we have officially brought up a few devices to be supported on Omni 7.1. They are: OPPO Find7 [find7] OnePlus One [find7op] Motorola Moto X Pure Edition/Style (2015) [clark] Nextbit Robin [ether] New Development Updates A flurry of activity over the end of last year and the first of this has brought a few notable things to update you on: Maxwen has essentially rewritten the following apps: MusicFX/Equalizer Calendar AppOps returns with the following updates and additions: Configurable columns Scrollable quickbar Option to disable media metadata lockscreen wallpaper Quick settings customization Gallery fixes That’s it for now – we’ll continue to keep you updated on new developments and things happening, and Happy New...

read more

Strengthening Communication in our Community

Posted by on 6:01 pm in Development, Features, General, Process

Strengthening Communication in our Community

One of the core tenets of Omni has been transparency: transparency in decisions, transparency in actions, and transparency in communication (to name a few). As we mentioned in our last update, we’ve been going through many changes over the past year and one of those has been in how we communicate internally and externally. In the past we have used IRC where we had our internal team channel and a few public channels for discussion and development. This worked well for a time, but as our team encountered real-life challenges became a bit of a challenge to remain connected – so, as many development teams do, we added Slack thinking it would solve things. It did – to some extent – but it also presented us with the challenge that we have a commitment to Open Source and using a closed-source, hosted solution like Slack didn’t fit that commitment. So, we pivoted and moved to Mattermost, an open-source, self-hosted alternative to Slack. Over the last month we have been using it, and it definitely has improved our workflow and increased our productivity as a team. The move to Mattermost was solidified for us due to the convenience of communication between maintainers and our core team was much better than on IRC for the following reasons (YMMV): constant IRC presence requires a bouncer or quassel, which generally cost money and/or are not available to all. many important topics of discussion quickly became buried in IRC between part/join messages and other irrelevant chatter. a private mattermost implementation allows us to maintain better communication over IRC as well as host the server on our own, making us completely self-sufficient That of course brought about the next level of questions, which was “what about our transparency to the community?” To address this, and to make sure that we continue to be connected to the community as we work to improve and grow OmniROM, we have created a bridge between our #omni channel on IRC and Mattermost. Over the coming weeks and months we aim to grow our communication with the community, and this seemingly small step is a great step in that direction.  ...

read more

Omni December 2016 Updates

Posted by on 5:18 pm in android-6.0, android-7.1, Development, Features, Releases

Omni December 2016 Updates

With Christmas and New Years fast approaching, it’s time to look at December 2016 and all we have been working on. Device Announcements Some new devices, and old favorites, are receiving updates courtesy of our Device Maintainers. Feel free to test them out, with the typical disclaimer that these are test builds, and as such know there may be issues which pop up until the device(s) move to Nightly Status. Android 7.1.1 Device Updates The good old Oppo Find 7 is not dead yet. Thanks to work done by maxwen, Darkobas, and Philipp it was a breeze to bring new life into this still solid device. You can find the test builds on XDA. Not to be outdone, the little twin to the Find 7, the OnePlus One, is also back into action thanks to Philipp and Darkobas. Wi-Fi Hotspot and SELinux Permissive are known issues at this time, but will be fixed soon. You can find the test builds on GDrive. Android One 2nd Generation (codename seed), the msm8916 variant of Google’s Android One project, now runs OmniRom 7.1.1 courtesy of arvinquilao, with able help from kldoc for camcorder fix. The test builds can be downloaded via AFH. Omni Welcomes Sony Xperia X Compact The Sony Xperia X Compact (kugo) has joined the Omni ranks thanks to oshmoun, the device maintainer, with help from humberos. Currently this device is on the Android 6.0 branch as there are still some missing functions for Android 7.x, mainly camera which is a work in progress. Team Updates OmniROM has evolved a lot since it’s creation, with many of its initial founding members currently taking a break for work or life reasons. Today we have a good, core group of device maintainers working to keep current devices in line where possible, and bringing on new devices as work load and availability of new device maintainers allow. One thing hasn’t changed, and that is that we are all passionate about Android and we really enjoy working together with our community to make OmniROM better every day. If you’re interested in joining the team and contributing to Omni do not hesitate to let us know. A few key notes of administration are: kldoc is taking over as device maintainer on the OnePlus 3 from Maxwen so that he can continue to focus on core features of Omni like OmniSwitch, OpenDelta, and so on Due to contributions from OnePlus and XDA, scanno, Bumble-Bee, and kldoc will be bringing up the OnePlus 3T as the initial device maintainers. Thanks for all of your support and we look forward to a great...

read more

Omni November 2016 Updates

Posted by on 2:22 pm in android-6.0, android-7.1, Development, Features, Releases

Omni November 2016 Updates

First of all, we’d like to apologize for our radio silence – we’ve been hard at work bringing Android 7.x to OmniROM and as such haven’t really been very “social” and for that we do apologize. With that being said, we wanted to provide a few updates on where we stand today. Jacob Whatley has done the long-needed care to, and update of, our Jenkins servers, and as a result we have rolled out fresh builds with the November Security Update 6.0.1_r74 for the following devices: bullhead toro angler manta shamu hammerhead suzu n3 maguro mako toroplus espresso3g espressowifi find7 find7op Make sure to visit our Downloads to find updates for the above. As if often the case with good news, there is a bit of bad: flo, the Google Nexus 7 2013 WiFi, has been dropped as a supported device due to lack of a maintainer. If you have the time and skills, or desire to learn, please feel free to reach out to us via @omni_rom / #omnirom / #omni. The updates which were performed on the Jenkins servers also included preparations for the upcoming 7.1 official builds. At this time we have not decided yet if we will be switching over to Weekly Builds, so look for news on that front in the near future. Google has not made 7.x development very easy as their 7.1 drop was not a clean upgrade from 7.0 – so we can only hope that 7.1.1 won’t be the same type of nightmare. We do thank you for your support, and look forward to providing you with more consistent updates. Featured image courtesy of...

read more

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