Some of the most interesting additions to Android often come from unofficial sources. Maligned though they may be, Google has incorporated many features previously only found in manufacturer skins into AOSP, and custom ROM developers add new features more or less as they feel like it, some of which are quite useful. For example, the CyanogenMod development team is working on a new integrated system for handling "locked" apps, applications that can't be accessed by the user without a password or other validation mechanism. Read More
The Galaxy Nexus is nearly as old as the Nook Tablet that CyanogenMod resurrected a couple of days ago with CM13, but it won't be getting that fresh of a software update. It'll have to do with a slightly older version of Android, but any third-party development on this forgotten Nexus is a welcome change from the state that Google left it in.
Officially, the Galaxy Nexus was abandoned at Android Jelly Bean 4.3. When KitKat was released in September 2013, two years into the Galaxy Nexus' lifespan, the phone wasn't deemed worthy of the new dessert flavor (allegedly due to the TI chip), but CyanogenMod's team of zealous and reckless developers braved the elements and kept supporting it with CM11 nightlies and snapshots. Read More
The ADT-1 was never released to the public, but handed out to developers after Google I/O 2014 as a test device for the new Android TV platform. It didn't get much attention from Google past Android 5.0.2, which was its last official update. However, developers are an unrelenting bunch and if they have an Android device lying around, you'd bet that they'll try to cook up ROMs for it as long as that's remotely feasible. (Exhibit A.)
So a few XDA members were tired of seeing the ADT-1 get shunned from OTA updates and decided to take care of the situation. Read More
CyanogenMod snapshots provide the most stable experience you can expect from the custom ROM, and now the latest batch is rolling out to devices. This time around you're getting the November security updates that Google released in AOSP earlier this month. Your device will still run Lollipop. Marshmallow won't appear until CyanogenMod 13. Read More
T-Mobile users with the latest devices (and sometimes with the latest software updates) appreciate the inclusion of Wi-Fi calling for those areas where the network doesn't reach or can't penetrate indoors. Of course, the fact that Wi-Fi calling is available is a good reason to abstain from flashing custom ROMs, even on multi-carrier devices like the latest batch of Nexus phones. Apparently that won't be a problem for much longer, at least if you're a fan of the CyanogenMod ROM.
Cyanogen Inc. employee (and former leader of the AOKP ROM team) Roman Birg posted the screenshot above to Google+, clearly showing T-Mobile Wi-Fi calling on an AOSP-style software build. Read More
The folks at CyanogenMod work fast. It was only two days ago that the AOSP code was updated with October's security fixes (following Google's promise to issue monthly security updates to Android) and now these changes have been merged into the custom ROM's code and are stable enough to deserve a "snapshot" label instead of the nightly status.
This isn't the first 12.1 stable(ish) release from CyanogenMod. The title goes to last month's snapshot which brought Android 5.1.1 to many of CM's supported devices. But this new build should be even more stable and reliable than that thanks to the new fixes. Read More
The CyanogenMod team continues to develop builds for new phones, and today we get support for two budget-oriented options that are popular with the unlocked crowd. The Moto E 2015, a phone with a relatively small screen and a tiny price, and the Huawei Mate 2, a phone with a relatively enormous screen and a price that's still pretty small, both have CyanogenMod 12.1 (Android 5.1) ROMs waiting for them on the official download site.
The Mate 2 is under the "mt2" codename, currently with three nightly builds available, and the Moto E 2015 is (for no obvious reason) labeled "otus" with two builds available at the time of writing. Read More
You knew this was coming sooner or later. Android Auto has been viewed as a mostly closed system, if not by nature of the software itself (which is technically open source) then by the fact that it's an extension of Android running on a big chunk of metal installed in your car. But some intrepid developers over on enthusiast forum AVIC411 have discovered a way to boot software directly from the SD card slot on Pioneer's NEX series of aftermarket Android Auto head units. That paves the way for custom ROMs in your car, or at least your car's entertainment system. Read More
Paranoid Android is a favorite in the custom ROM community, so there will likely be many people who are happy to see a build based on the latest version of AOSP.
This release took a while to bake in the oven, and there's a solid chance upcoming versions will take longer. After losing several key contributors to OnePlus, Paranoid Android's core team lacks the manpower it once had. It needs new muscle to keep the changes coming and welcomes contributions. In the meantime, the project is switching from a weekly release schedule to a "release when appropriate" timeframe. Read More