Blog

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

Completing the Galaxy Nexus Family: Sprint Variant (toroplus) Now Added To Nightlies

Posted by on 2:27 pm in android-4.4, Development, Devices

Completing the Galaxy Nexus Family: Sprint Variant (toroplus) Now Added To Nightlies

The Galaxy Nexus was, and some might argue still is, a venerable device. Launched by Google as the first phone to showcase Android 4.0, AKA Ice Cream Sandwich, it boasted a variety of new features that one would consider commonplace today, but was not previously available. This included a 720p HD display and a zero shutter lag camera. Unfortunately, Google decided that it was not worthy of the 4.4 KitKat treatment, and so official AOSP support for it was dropped with 4.3 Jellybean. However, the custom ROM community was not just going to take this lying down. Through some hard work by dedicated devs and community members, the Galaxy Nexus remains alive today. For months now here at Omni, we have supported the GSM variant (maguro) and the Verizon LTE variant (toro), but not the Sprint LTE variant (toroplus). This was because we lacked a proper Galaxy Nexus maintainer, and even though we supported the former two, we considered them on “life support” because of this. This all changed recently when community member MWisBest stepped up to be our new maintainer. Thanks to his work, Galaxy Nexus devices have received several optimizations and fixes, and the Sprint LTE variant is now fully supported by Omni and added to nightlies. Head over to the download page if you own a Sprint Galaxy Nexus to start enjoying some Omni goodness! As always, bug reports are welcomed on our JIRA...

read more

OmniROM Nightlies Land on the Sony Xperia L

Posted by on 10:08 pm in android-4.4, Development, Devices

OmniROM Nightlies Land on the Sony Xperia L

In the custom ROM community, we find that developers focus mainly on high-end devices while the lower-end device often go ignored. Most of the time it is not because these devices are not capable enough to run custom firmware, but simply because there is a lack of interest. However, that is not the case with the Sony Xperia L. Codenamed “taoshan”, the L has a 1GHz dual-core Qualcomm MSM8230 with Adreno 305 graphics. Nightlies have been kicked off for this device as of today, thanks to the efforts by community member Olivier. Community members are a crucial part of Omni, and we always welcome new members into the Omni family, whether you are a user or a developer. This also serves as a reminder that just because newer and greater devices have come out, we do not simply neglect older, less capable devices. Owners of the Xperia L may head to the download page to get started on enjoying some OmniROM KitKat goodness! As always, updates later on will be available through our OpenDelta incremental updater, as this is now an officially supported device. Lastly, should you have issues, please feel free to report them to our JIRA...

read more

OmniROM Nightly 4.4.3 Builds Incoming

Posted by on 3:02 am in Development, Releases

OmniROM Nightly 4.4.3 Builds Incoming

It’s that time of the release cycle again – Google has released Android 4.4.3 to AOSP. Thanks to the tireless work of our own Xplodwild, Omni has now merged the changes to Android 4.4.3, and these will be rolling out in nightly builds for the 5th June. As I write this, builds are scheduled to start in around 20 minutes or so, and will appear at our download pages once they are completed. They will also be available through Omni’s inbuilt delta OTA updater, as always. Our merged code is on our Github, as always – hopefully it may save other developers time in getting Android 4.4.3 merged into their trees. This rollout should go smoothly, but as always, with big upstream changes, there could be the odd hiccup here and there with some devices. We hope you enjoy a first taste of Android 4.4.3 in a custom ROM. And thanks once again to Xplodwild for his stellar job in getting the merge completed in record-quick...

read more

Custom Hotwords From the Home Screen

Posted by on 8:59 pm in Development, Features

Custom Hotwords From the Home Screen

Google Now has become a great tool for those who like to have information quickly at their fingertips. The ability to use your voice to search without having to type it out, much less think about it, is appealing to many. The list of commands you can either tell Google Now, or have automatically available via contextual analysis, continues to grow with each new release. That list of voice commands, however, is something already pre-determined by Google – and for some that just isn’t good enough. Omni Developer XpLoDWilD has been working on a new feature (appropriately named Custom Hotword) which gives you the control you probably desire. Via the AOSP Launcher3 (different from the Google Now Launcher) XpLoDWilD has provided a way for the user to create custom hotwords which can be used to setup a phrase to startup Chrome, dial your spouse, or bring up the camera – all from an unlocked screen. No need to first say “Ok Google” – instead just go into the Launcher Settings (long press open space on the home screen and choose Settings), scroll down to Hotwords, and Customize hotwords. You can setup as many hotwords and as many actions as you can imagine. And since this isn’t a wakeup command like “Hey Snapdragon”, the only battery consumption is when the screen is on the home screen – just like Google Now. When the screen is off, there’s no consumption. See the video below for a demonstration. You should be able to make use of this feature as early as tomorrow’s nightlies (May 28). And stay tuned for more to come as we break our long radio...

read more