CarbonROM Blog

One Ring to bind them

I know, my headlines can be very confusing at times. However I promise it makes sense this time.

Today is the day that Joe and Kennedy were looking forward to since Christmas of 2017. It’s their wedding day.

From everyone in the team we wish them lots of love and happiness!

Some of you might wonder why we brought that up. The reason is that the CarbonROM team had a crucial role in their engagement. You can read the full story on Android Central.

A new Hope

Most you of probably noticed already. We surely didn’t have the most reliable Server host.

After a total 12 days of downtime they eventually told us that our data is lost. Again. Not more than 4 weeks after they replaced the HDDs because they were faulty and caused a partial dataloss.

As we said on twitter already, we do not longer host our Infrastructure at CloudSouth. Also we HIGHLY recommend you not to do so either. We understand that Hardware faults can happen, but the way their support works (or doesn’t) and the amount of time they take to respond to support requests is unacceptable.

However, there’s also good news. We’re now running a c2.medium.x86 (which, apart from it’s name, is anything but medium) thanks to a sponsorship from Packet.com! Big thanks to them for their super awesome support and immediate response. We really appreciate it.

Most of our infrastructure is back already, and the last bits will follow tomorrow (that is get.carbonrom.org) along with a new set of builds for both, Oreo and Pie.

The Oreo builds are, simply said, because we are too lazy to manually add the builds to the get.carbonrom.org database again. The Pie builds will be a normal weekly release and contain plently of bugfixes about issues we got reported on the initial builds.

Small Changelog:

You should get your usual Update Notification on CarbonDelta. However, due to data loss there we won’t provide a delta update this time, so don’t be afraid when CarbonDelta asks you to download a full update.

As always, let us know when there’s any other Bugs or Feature Requests.

Happy Flashing!

We're live!

The time has finally come, we’re going official.

After Server issues, and several rebases due to Google’s Upstream doing the same, we’re finally satisfied with the ROM to make it officially available to the public.

The new CarbonROM revision 7.0 is codenamed Opal, and is currently based on android-9.0.0_r35 (thats the April security bulletin).

As always, you can find the builds on https://get.carbonrom.org/. The Unofficial XDA threads have been updated to reflect the new download links and information. Please note that due to custom signature Keys you MUST perform a clean install when moving from an Unofficial to an Official build.

Also it is recommended that you perform a clean install when coming from Noct. Whereas some devices were tested to perform an upgrade to Opal sucessfully, some where also discovered to require a clean install. That mainly affects devices using Full Disk Encryption (like the Nexus 6 and Xiaomi Redmi Note 4) because the encryption code had some major changes in Pie (actually it was removed by Google and readded by CAF). That means you need to remove your previous encryption (use “Format data” in TWRP) and reencrypt on Pie if you want to do so.

With new features like Aggressive Battery, a newly designed performance vendor, the addition of DUs Theme Engine and many more coming we feel like this might be our best release so far. Let us know what you think.

The initially supported devices are:

More devices will come at further releases, some of them even as soon as next week.

Also, this is the first time ever we will keep on maintaining the older branch. That means you will still get monthly security updates of Noct on the devices that do not support Pie yet.

For now, Happy flashing and we hope you’ll enjoy the ROM as much as we did creating it!

P.S: This is also the first release that is officially lead by Christian. Patrick and Ryan put down their duty as Project Leads. We’re wishing them the best on their further endavours ;)