Training in Quarantine – Day 191 and other updates

My last logged walk was 23rd October. I’ve been slacking off logging runs since then, so this is my first logged run since then, even though I have been doing near-daily runs since then, so I’m skipping through to Day 191 since I’ve done 10 days of walks since then.

I’ve also got a few other updates.

My house purchase fell through a while ago so I have been actively house hunting a lot and my past few Saturdays have been spent house viewing. Viewing during the day is tricky unless I take time off to house hunt.

Dealing with different Estate Agents is a pain, with some not even bothering to give you the time of day, let alone

I also upgraded my phone to Android 10 LineageOS and I’ve been having quite a few issues with internet speed and stability. I’m seriously considering forcing a downgrade back to Android 9. In the meantime, I might switch from Adoptable Storage back to portable storage to see if that helps with stability.

Oh, and it’s frickin’ COLD.

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

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

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

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

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.

%d bloggers like this: