We know, we know. It’s been more than a week already. Last few weeks have been rough as everyone was (and still is) occupied with studies and exams.
However, in the few minutes we were able to spare some very interesting things changed.
Along with the typical under the hood performance improvements you’ll mainly notice the following:
- As of today, the May Security Patches (OPM2.171019.029.B1) have been merged, see https://source.android.com/security/bulletin/2018-05-01 for more.
- Access issues with external media (like SDCards) have been fixed
- An issue with AOD, Screen off Animations and Auto Rotation causing App FCs has been fixed.
- HAL1 recording on legacy devices has been fixed. That means 4K Video Recording and 720p at 120FPS for the Xperia Z2/Z3/Z3 Compact/Z2 Tablet
Along with the fixes, we’re happy to announce that new maintainers joined the team and old maintainers got their devices back up for Oreo. That means that Noct now additionally supports these devices:
- Google Pixel (sailfish)
- Google Pixel XL (marlin)
- Google Nexus 4 (mako)
- Xiaomi Mi A1 (tissot)
More devices are getting finalized as you read this, and we’re always happy to welcome new maintainers too! When you have a device running Carbon and you want to support it officially, just make sure its running on enforced SELinux and on user builds, then send us an email to email@example.com.
Happy secure updating and (for the shinano users) happy video recording 🙂
See you next week (or relatively soon after that ;))
P.S. We noticed that plenty of you reported issues with the error message to update the vendor partition at boot (even when your device doesn’t have one). That’s caused by some recently merged commits that needed Device sided updates, which didn’t made it into this weeks build for all devices (sorry for that). HOWEVER: It is ONLY a Display error. There is no impact on the ROM or anything. We’ll fix it in next weeks build. Sorry for the inconveniences.
P.S. To the tissot users: As our builds are custom signed, the payload.bin is signed with out keys. If that key doesn’t match the one in /etc/update_engine/ the build will fail to flash.
On other devices this has been solved inside TWRP already (the signature check is disabled there), however that doesn’t seem to be the case for tissots official TWRP yet. We therefore made a zip to replace the key with ours that you need to flash before the the Carbon Build. You can find it here. As this is a ramdisk file, the edits will be gone after a TWRP reboot, so you need to flash it before every time you want to update. We’re working on fixing TWRP ASAP.