Spring 2017 Omni Updates
Mar31

Spring 2017 Omni Updates

Spring is all about the old dying out and new life coming – which for us means there are a number of new things happening at Omni. We’ve been working on features, added new devices, and even had new people join the team. So let’s get right to it shall we? Features At Omni we have always been about adding solid features which enhance the experience while still giving the user control, while also not just adding them for the sake of adding. There’s a purpose to everything we do. Music After searching for a solid replacement to the solid Apollo, which has been on minimal life support for a while now, we’ve decided to base on the GPLv3-licensed Phonograph. We feel that it is a good base for the time to come and will allow for us to add new features which will benefit the community as a whole. Oshmoun did a great job in getting it setup to build with the ROM but still allows for using Android Studio for development. Wallpapers, Header Packs, and More We began a new project recently called OmniStyle which allowed for styling the status bar headers, and now we’ve added functionality to allow wallpapers to be “styled” as well. We have added a new wallpaper picker activity into OmniStyle and then also integrated it into Settings under the Style section. We are searching for new contributions to wallpapers, header packs, boot animations, and sounds which exhibit the Omni branding as well as an Omni theme (more on that later). If you want to contribute wallpapers, you can do so in our G+ community. We’d also like to thank the following for their contributions so far: Custom sound contributions from Vincenzo Mario Cristi (ringtones, alarms, and notifications, with system sounds to come) Wallpaper contributions from JayRod JP Kenji and Siddharth Gupta Header pack contributions from Travis Hall and Syed Sajid OMS and Substratum Laurent has been merging all of the commits needed to enable Omni to support OMS and Substratum, along with fixing any of the merge conflicts which could occur. There are two types of commits to look for: OMS, OMS 7 or more generally OMS* deals with OMS and Substratum root mode. Note that the root mode will be soon deprecated. OMS rootless is the same but with rootless mode. The rootless mode requires all OMS* commits + specific rootless commits. Soon to come will be a new project, called “Proper Resources” for themers to fully customize Omni. More to come on that soon. Devices We have added the following new devices: Samsung Galaxy Tab S2 (T813) [gts210vewifi] Sony Xperia X Compact [kugo] Sony Xperia...

Read More
New Year, New Month, New Security Updates
Jan05

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
Dec27

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
We Have Lift-off! 5.1.1 Lollipop Nightlies Begin!
Jun21

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

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
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