Cyanogen’s fork is beginning to take shape. Currently my devices aren’t showing but fingers crossed it will.

Few points worth noting from their site:

• The build roster is ever growing, but we are supporting Marshmallow and Nougat capable devices.

  • We’ll list the 80+ devices in a separate post.

• Our release cadence will be ‘weekly’ by default (to be nice to all the donated hardware).

• We will NOT be shipping root baked into the ROM.

  • Root will be a downloadable zip based install similar to gapps installation (only need to flash it once).
  • Home builders that want to bake su back into the ROM can use the command ‘export WITH_SU=true’ prior to building.

• Our official builds will all be signed with a private key for authentication and signature permission control

  • This will not break, prevent or stop any ‘unofficial’ builds.

  • Key verification info can be found on the wiki Verifying Build Authenticity page

However, also notable and I’m really happy about this:

Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.

• Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.
• This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
• This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
• This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
• The process for this installation will be as follows:
  • Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).
  • Reboot
  • Install LineageOS weekly build
  • Reboot
  • Re-setup your application permissions

Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.

All systems operational

Source: Update & Build Prep – Lineage OS – Lineage OS Android Distribution

Open source Android ROM project dies, developers launch fork.

Source: Cyanogen Inc. shuts down CyanogenMod in Christmas bloodbath | Ars Technica

So, CM is dead, but like with most things in the open source world, things will be forked, especially if there’s a disagreement between the two. In this case, rather than compete, it’s a desire to keep the project going.

Related articles

• After having its infrastructure shuttered, CyanogenMod will live on as Lineage
• This startup once thought it would 'put a bullet through Google's head' - now it's killing its own operating system (GOOGL)

So I updated my S5 to Android 6.0.1 using Cyanogenmod, and I’ve noticed some slight lagging. Apps tend to close themselves randomly, normally when less apps are running than on Android  5.1.1. Also, when using the tethered connection, there’s some lag there too, causing my online games to judder. Though that part is only hypothetical, I’m going to test this by downgrading my phone back to 5.1 and verifying whether there’s lag on my connection there. If there isn’t, I’ll report this as a bug.

Further to my previous post, here’s a run down of what happened.

I’m currently running Cyanogenmod or a variant of it, which has lots of nightly builds - normally I choose not to flash but on Sunday, I decided to try. Probably a mistake.

Cyanogen updated from Android 5 Lollipop to Android 6 Marshmallow, which meant after I flashed, I was getting huge numbers of “sorry but xxxx crashed”. I suspected the Gapps was out of date or incompatible with the android version I had, and I was right - a different version was needed. So I flashed that also but that didn’t work, so I rolled back to my last good backup, which was from November 2015, that restored fine, and I’m back to where I was, minus a lot of app changes and updates needed (I uninstalled/reinstalled a lot of apps since that backup), fixed that, reupdated my apps, and redid both my app and my Nandroid backups so I’m good to try again sometime.

I lost a good hour to two hours over this, so let this be a reminder to make sure you have good backups before flashing. I was lucky I only lost 2.5 months of changes, and that was easily fixed, but losing ALL your data because you don’t have a backup is never fun (I’ve been there)

Related articles

• [ROM] [6.0.1] [MARSHMALLOW] CyanogenMod 13 for Nexus 9 LTE
• CyanogenMod 13.0 Nightly Builds Available for Asus ZenFone 2
• CyanogenMod 13 Nightly: SetupWizard has stopped working.

I’ve been contemplating flashing my phone since the guys at Cyanogenmod haven’t released any new ROM versions since 2013. Looking around on the XDA forums, I’ve found plenty of releases by other people and teams, some of which are the new KitKat version. So I downloaded and put those on my phone, but learning from past mistakes, I made sure I had a backup. My recovery is the TWRP, so I did a backup on that tool, then flashed the ROM. It booted up fine, but got loads of FCs, so I went back and restored my backup. Or so I thought. Going back into my pre-KitKat ROM, left me with a factory-resetted version of a good ROM. So I can to reconnect my Google accounts, install Titanium Backup and its key, then restore my backups from Titanium. Seriously, buy Titanium Backup, it will save you HOURS of time redownloading, reinstalling, and reconfiguring your applications.

So now, I’m running my application restores, then I’m going to reboot and check it all works, then download and install the latest TWRP recovery (I suspect mine might be out of date since I haven’t used it for a long while), and do another backup, then try again.

If you're not on CyanogenMod there is still hope however, as Dutta revealed over the weekend that he has it working on any rooted device running Android 4.4.1, and may have a way for it to operate even on hardware that's not rooted. Koush has been a busy guy lately, also revealing that Google may add Android-to-Chromecast mirroring soon and releasing a new version of his media streaming AllCast app, we almost feel bad about hoping the Cast SDK adds on a few new opportunities.

via CyanogenMod 11 Screencast video recording is as easy as taking a screenshot.