OmniROM integrates Android 4.4.3 into nightly builds

At the height of the Android 4.4.3 release frenzy, OmniROM made an important announcement. It has kicked off nightly builds of supported devices that includes the latest Android version, thereby showing that the project is still pretty much alive and kicking.

By itself, Android 4.4.3 isn't exactly an earth-shattering update. Sure, it does bring a couple of new features, like a redesigned dialer app, but most of its contents are bug fixes and performance tweaks. Naturally, the moment images and source code hit public sources, custom ROMs started taking the road towards rebasing their code and builds on this version. Fortunately, OmniROM is one of those and, even better, they are telling the world about it.

Aside from the brief preview of a new feature last week, OmniROM has been rather silent on the public front, especially on its website and blog. Make no mistake, code has been moving behind the scenes, but unless you're privy to that part of development, you'd think that the project was stagnating, which is definitely not the case. This public announcement, not to mention the new nightly builds, could very well serve to reignite some interest in the fledgling Android ROM as it treks the road towards its first stable release.

And OmniROM might be one ROM worth waiting for or looking into. Aside from their commitment to the spirit and letter of open source software, they also have pretty ambitious and interesting features planned, which will hopefully all see the light of day, in one form or another. This list includes the recent hot phrases preview, a different kind of multi window implementation, and a new app switching feature. Hit the links below to read more about these features and make sure to keep tabs on our OmniROM tag portal if this project has piqued your interest.


CyanogenMod issues advisory for several HTC devices

The CyanogenMod dev team has made an important PSA (public service announcement) that will critically affect those running nightly builds on a number of HTC's smartphones. Due to changes in one of the important processes for getting a Linux system, like Android, up and running, those devices will need a more recent version of the CWM or TWRP recoveries.

The full list of affected devices are as follows:

  • evita – HTC One XL
  • fireball – HTC Droid Incredible 4G LTE
  • jewel – HTC EVO 4G LTE
  • m4 – HTC One Mini
  • m7 – HTC One [GSM]
  • m7spr – HTC One [Sprint]
  • m7vzw – HTC One [Verizon]
  • ville – HTC One S

Starting with the nightly build dated 20140501, these HTC devices will be making use of a new fstab (for File System Table) layout, which will require kernel support in recoveries. However, almost all current versions of recoveries out there in the wild do not yet have this, which means that users will have to update their CWM version first before installing the nightly build. Those using TWRP will have to temporarily use an unofficial version until TWRP comes out with an official updated release.

Those who encrypt their devices using Android's built-in tool will have to take a few more steps before they actually install an updated recovery. The process consists of backing up the encrypted /data partition first and restoring it afterwards, though it will be in a decrypted form at first. The latest nightly will also be moving the encrypted information from /data to /extra but only for the following devices:

  • evita - HTC One XL
  • fireball - HTC Droid Incredible 4G LTE
  • jewel - HTC EVO 4G LTE
  • ville - HTC One S

Those with affected devices on CM nightlies should check and follow the instructions from the link below. It might sound a bit complicated and involved, but such is the price of running a bleeding edge version of anything. You are always first to get new features, but also first to encounter bugs and sometimes destructive changes.

SOURCE: CyanogenMod (1), (2)

CyanogenMod switches on CyanogenMod 11 nightly builds for dozens of devices

The makers of the one of if not the most popular custom Android ROM is proceeding full steam ahead with its transition to an Android 4.4 codebase. Now it has activated the nightly builds for devices that can support CyanogenMod 11.


Last week, the CyanogenMod team announced the first CyanogenMod 11 snapshot, CyanogenMod 11 M1. This snapshot, however, was limited only to more recent Nexus devices. The team did promise that it will soon be enabling nightly builds, and now its announcing which supported devices will fall under which CyanogenMod version. This list accounts for all 156 officially supported devices compatible with CyanogenMod 10.0 and higher.

Dozens of devices, including the Galaxy Nexus, will be receiving nightly builds of CyanogenMod 11, which is based on Android 4.4. But even more than that, Android 4.4.1, which has just started rolling out to Nexus devices, is already being merged into the codebase. This means that the next round of nightly builds will soon include the latest maintenance update as well. Unfortunately, this announcement also spells the end of nightly builds for devices running CyanogenMod 9 or older, to give way to CM 10.2 and CM 11.

The list of devices, which you can read from the source link below, is not yet exhaustive nor is it final. Some devices under CyanogenMod 10.2 are expected to move up to CyanogenMod 11 over the next few weeks. Nightlies are, of course, considered to be raw versions, so they should be installed and used with care and a bit of knowledge of the risks involved.

SOURCE: CyanogenMod

OmniROM drops Android 4.4 Kit Kat based nightly release

There are plenty of third party ROMs available for Android users to pick and choose from. Some are better known than others and some have been around for longer, and while we often look towards Cyanogen and Paranoid Android as highlights here, there is another, newer option with OmniROM. The OmniROM team, which is made up of a few well known Android developers have released a Kit Kat based ROM with support for 15 devices.


Keeping in mind, these ROMs are considered nightlies. Or in other words, those choosing to go this route may not have a perfect experience and may run into a bug or two. We suspect those following the available ROMs already know the potential with that, so here is the list of supported devices.

  • Nexus 4 and Nexus 5 smartphones
  • Nexus 7: 2012 3G, 2012 WiFi and 2013 WiFi
  • OPPO Find 5

Otherwise, the remaining handsets are all from Samsung and include the; Galaxy SII (i91000G), Galaxy S II for AT&T (SGH-i777), Galaxy S III (i9300), Galaxy S III LTE (i9305), Galaxy Note, (N7000), Galaxy Note II (N7100), Galaxy Note II LTE (t0lte) and the Galaxy Note II for T-Mobile and AT&T. While no timeline was given, there was mention of upcoming support for HTC and Sony devices as well.

Along with the device support, there was also mention of the new features that are found in this Kit Kat based ROM. The first up here is for incoming calls. Here the OmniROM team touts this as being done the non-intrusive way. This is shown in the image sitting up higher in the post and basically means you will get new call notifications by way of a pop-up card that slides up from the bottom of the screen.


OmniROM also includes ActiveDisplay and Apps permissions which can be found by navigating to Settings -> Apps permissions. Another big addition is the DSP Manager enhancements. Here we are seeing details about how you will be able to adjust the center frequency of the bass boost and a new stereo widening effect which is said to enhance the stereo image of your songs.

VIA: Android Police

SOURCE: OmniROM (1), (2)

CyanogenMod announces nightly builds for LG G2, Nexus 7 LTE, and Nexus Q

Its formation into a company and partnership with OPPO, as well as some amount of controversy arising from that, has not put a damper on CyanogenMod‘s activities. As previously shared, they have mighty ambitious plans up ahead, and that starts with adding a few new very recent Android devices, and an odd old one, to their nightly builds list.


CyanogenMod has just added nightly builds for LG‘s latest flagship, the LG G2. The 5.2-inch smartphone made its way into the market last August and possesses some rather unique hardware and software features, including rear-side volume and power buttons, KnockOn display activation and deactivation, a few new multitasking features, and more. You can read all about those in our full review of the device here. Initially, both the international and the Verizon G2 versions had nightly builds available, but CyanogenMod had to pull out the Verizon build temporarily because of problems with the Radio Interface Layer (RIL), which is essential for phone functionality.

The team has also announced a new maintainer who will take care of looking after the LTE variant of the Nexus 7 2013 edition. Of course, the Nexus 7 already runs a vanilla version of Android, unencumbered by carrier and manufacturer addons, but there will definitely be owners who will prefer CyanogenMod’s own blend. For now, only the source code has been put up in CyanogenMod’s GitHub repository but nightly builds for the device will be starting soon. In the meantime, one can always fill in the waiting period with a review of our impressions on Google‘s latest 7-inch masterpiece.

Quite amusingly, the team has also started nightly builds for the almost literal oddball Nexus device, the multimedia-oriented Nexus Q that was first unveiled last year and has quietly receded into the background. The few who have had been able to get their hands on the device might find new hope in CyanogenMod soon, as the first nightly build of CyanogenMod 10.2, with Android 4.3, is now up.

SOURCE: CyanogenMod (1), (2)

Sprint and Verizon Galaxy Note 2 have begun getting CyanogenMod 10.1 Nightlies

cyanogenmod When a new device is supported by CyanogenMod, it’s always cause for celebration. The world renowned custom AOSP ROM is among the most popular custom ROMs in the world, with more than a million users worldwide. Now, they’re numbers will continue to grow as CM nightlies are available for the Verizon and Sprint Samsung Galaxy Note 2.

The GSM versions of the Note 2 have had CM support for some time. These include the international variant as well as T-Mobile and AT&T. So it’s really nice to see the CDMA variants get picked up as well. We know Sprint and Verizon owners will be really glad.

Since these are nightlies, the standard disclaimers apply. These are the bleeding edge of CyanogenMod development. So there is always the risk of features not working or the ROM itself having issues. Never to fear, nightlies are generated nearly every day with new code merges and bug fixes. So it’s only a matter of time before things get really stable.

Will there be any stable CyanogenMod builds in the near future?

We all know better than to ask for ETA’s. However, if these nightlies are anything like the nightlies for the AT&T and T-Mobile variants, then users will be delighted. Just because it’s a nightly doesn’t mean it is unstable, it just means the risk is there. So the only way to know for sure is to check out the Gerrit or try it out.

Head over to and get to downloading. Don’t forget the Gapps! Will anyone be flashing this tonight?

Related Posts

CM10.1 nightlies arrive for the CDMA Galaxy Note II

Some good news for CyanogenMod fans that happen to be sporting a CDMA Galaxy Note II. It looks like CM10.1 nightlies have finally arrived. As always, we offer the warning — the nightly builds, while generally stable, are nightlies for a reason. Simply put, these are early builds and probably best when not used on your primary device.


With the warning out of the way, those who have played this game before, you can download the ROM (for the Verizon and/or Sprint Galaxy Note II) from the website. Those who are looking to begin using CyanogenMod for the first time — CM10.1 will bring Android 4.2 Jelly Bean. First time users will also want to prepare for the installation by reading the directions. And then maybe reading them a second time just to be on the safe side.

While this does take some work to get installed, the process is detailed quite nicely at this point. In fact, it comes down to flashing the latest ClockworkMod-Recovery, booting into recovery mode and then flashing the CM10.1 and GApps zip files from your SD card. Well, that is a simplified version anyway. Keep in mind, there are slightly different steps for those using CyanogenMod for the first time, or for those upgrading from CM10 or even an earlier version of CM10.1.

For a flip side here, while we are normally big fans of running CyanogenMod, in the case of the Galaxy Note II — you may want to give some second thought because you will be losing some of the TouchWiz specific features. For example, multi-window and the S Pen will be going away should you go the way of Cyanogen on your Note II. Bottom line here, in this case we may go as far as suggesting sticking with the stock ROM and maybe looking towards a launcher to further customize the look and feel.

[via xda-developers]

Nexus Q gets CM 10.1 nightlies, not feeling so left out now

Nexus Q

Granted, Google is not even selling the Nexus Q anymore. Granted, the only people who have the Nexus Q in their living room are the minority who pre-ordered it. In any case, CyanogenMod has decided to give this much beleaguered device a breath of fresh air — CM 10.1 nightlies are now available for the elusive media streamer.

The standard disclaimer applies; keep in mind that these are nightlies and could contain a variety of bugs that could affect the usage of the device. However, it might be a reasonable bargain considering that this will bump up you Nexus Q to Android 4.2.1 from 4.0.4. To grab the latest nightly, hit up the source link below. Remember, the codename for the Nexus Q is ‘steelhead’, so look for future updates under that codename.

Related Posts

CyanogenMod releases first nightly builds for the Google Nexus Q

Google may have banished the Nexus Q from the Play Store a while back, however it looks like the device isn’t totally dead yet. Well, it may be in the eyes of Google, however the folks at CyanogenMod have just released the first nightly build for the media streaming device that never really took off.


That being said, the CyanogenMod nightly build for the Nexus Q is dubbed steelhead and will bring Android 4.2.1 Jelly Bean. Of course, while this may be exactly what some Nexus Q users have been waiting and hoping for, there are some catches that you will likely want to know up front.

The folks at CyanogenMod are describing this release as being “fully functional” but with one caveat. That caveat may be enough for some to stop thinking about running this nightly and sticking with the original software. The original @home functionality will no longer work once you have the nightly build up and running. Taking that a step further, it was said that is is unclear if it will ever work.

The ROM can be downloaded from the CyanogenMod website and the installation process is similar to other Nexus devices. In other words, boot into fast boot mode, unlock it and then flash the recover. Another bit worth mentioning, the navigation during the recovery process is done using the Q. You will need to rotate the ball to navigate the menu and tap when you need to select. And then once in with CyanogenMod up and running, you can navigate with a mouse — either wired or Bluetooth. All said and done, it looks like the folks at CyanogenMod have given the Nexus Q a little bit of extra life.

Device Specifications and Information
Device Info
    Device Name : Nexus Q
    Manufactuer : Google
    Carrier : NA
    Announced Date : June 27, 2012
    Release Date : June 27, 2012
    Also Known As :
  • Screen Size : Inch
  • Resolution :
  • Screen Type : NA
Dimension & Weight
  • Height : 4.6 Inch
  • Width : 4.6 Inch
  • Depth : 4.6 Inch
  • Weight : 923 Grams
Battery & Power
  • Battery Capacity : mAh
  • Talk Time : NA
  • Stand By Time : NA
    Android OS:
  • 4.0.x
    Audio Playback:
  • AAC
  • AAC+
  • AMR
  • MID
  • MP3
  • WAV
  • WMA
    Video Playback:
  • h.263
  • h.264 / AVC
  • 3GP
  • MPEG-4 (MP4)
  • WMV
    CPU : OMAP4460
    CPU Clock Speed : Mhz
    Core : 2
    Ram : 1000 MB
    Internal Storage : 16 GB
    Front Facing Camera :
    Camera Resolution : NA
    QWERTY :
Cellular Network
Device Connectivity
  • 802.11b
  • 802.11g
  • 802.11n
  • Bluetooth 3.0
  • A2DP
    FM Radio :
    NFC :

[via Google+]

Paranoid Android custom ROM to introduce expanded desktop soon

paranoid android
Paranoid Android is one of the most unique custom ROMs out there. It is an AOSP build that is based on the popular CyanogenMod. It is also known for some pretty radical things, such as its hybrid mode. Hybrid mode allows devices to run apps and menus in a hybrid of phone and tablet modes. Their next big feature is the expanded desktop.

Paranoid Android’s expanded desktop could also be called a radial menu. It works pretty easily too. People using the ROM would swipe up from the bottom of the screen and a radial menu will appear. From there you have a choice of the customary home, back, recent apps, and menu (where applicable).

This would replace the standard navigation bar that most AOSP ROMs carry now where the software buttons rest permanently across the bottom of the screen. The immediate pro of extended desktop is that it gives you that extra screen space that used to be taken by the nav bar.

According to Paranoid Android in this Google+ post, the expanded desktop should be available in an upcoming string of nightly builds. To activate it, hold the power button until the menu comes up, and select the expanded desktop.

This is pretty nifty, where did Paranoid Android get the idea?

Radial menus have been around for quite some, just not on mobile devices. As many Linux users will tell you, there are third party docks that allow for radial menus, such as Cairo Dock. This idea has also been thought of for Android itself by Google. As Patent Bolt reported some time ago, Google actually filed a patent application on radial menus. At the time, the talk was that it would be included in Android at some point. It didn’t happen with 4.2 Jelly Bean, but there’s always 5.0 and beyond.

In any case, this is a really cool feature and a lot of people are sure to enjoy it. It isn’t available yet, but if you’d like to see it in action, check out the Google+ post linked above and watch the video. Is anyone going to be giving this a try when it becomes public?

Related Posts