New CyanogenMod 13 Snapshot Builds Rolling Out

BY Ben Patterson

Published 16 Aug 2016

Cyanogen_logo

The CyanogenMod team today released a new snapshot build of CyanogenMod 13 based on Android 6.0.1. The latest snapshot build packs in a lot of new features, enhancements, and security patches.

One of the highlights of the latest snapshot build is the new custom boot and dexopt screen, which is AMOLED friendly, looks pretty, and displays more information compared to Google’s implementation. Other changes include Gello browser, CM’s new Snap camera app, Lockscreen Weather plugin support, improved LiveDisplay, and more. If you are already running a nightly build of CM13 that was released on or after August 1st, you already have access to all the changes that the latest snapshot build packs.

A mini changelog of the update is as follows:

  • Wi-Fi Tethering – automatically turn off hotspot after X minutes of inactivity
  • Profiles – add notification light controls
  • Do Not Disturb/Priority Mode – add notification light controls
  • Privacy Guard/App data usage – Restrict apps to Wi-Fi or Cellular data only or block all internet access, per app
  • Bluetooth Devices battery support – For compatible devices, a new battery icon will appear in the status bar to show the paired devices’ battery level
  • Lockscreen Wallpaper picker makes its return
  • Lockscreen Weather and new Weather plug in support – see weather blog post
  • Lockscreen Blur support (on a per device basis) and the ability to disable the effect
  • Live Lockscreen support
  • New LiveDisplay hardware enhancements and API
  • Snap Camera (per device basis)
  • Gello Browser (per device basis)
  • Lots of translations – shout out to the CM translations team on CrowdIn
  • Cyanogen Apps support (see blog post, x86 is not supported yet)
  • Additional CM SDK APIs
  • Security fixes galore

A full changelog can be found here.

While this snapshot build also contains all the security bulletin patches released by Google this year up until August 5th, it is still vulnerable to the QuadRooter vulnerability. This is because one of the vulnerability is within OEM binary blobs, whose source code access the CM team does not have. This means that some of these devices will continue to remain vulnerable to QuadRooter exploit, though with other security checks in place from Google, you really should not worry about it.

You can find a list of devices getting the latest CM13 Snapshot build and their download links here.