[7.x.x][WEEKLIES] CarbonROM | cr-5.1 [sailfish]

[Myself5]

Who's back? We're back.​

CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.

Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.

Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:

1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.

Downloads:
Get CarbonROM
GitHub
Gerrit
Kernel source

Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!



XDA:DevDB Information
CarbonROM, ROM for the Google Pixel

Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM

ROM OS Version: 7.x Nougat
Based On: AOSP

Version Information
Status: Nightly

Created 2017-01-01
Last Updated 2018-03-17

 

[quangtran1]

Very nice! Ask and you shall receive, right?

 

[Myself5]

Very nice! Ask and you shall receive, right?

Official builds are currently compiling and will be uploaded once done. The unofficial build with Gapps will be linked to in a post when I find some time.

 

[quangtran1]

Official builds are currently compiling and will be uploaded once done. The unofficial build with Gapps will be linked to in a post when I find some time.

Thank you! Happy '17! I've always liked Carbon ROM.

 

[aholeinthewor1d]

Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.

Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.

Thanks!

 

[quangtran1]

Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.

Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.

Thanks!

gApps have always been problematic with every additional security layer added. With different slots, but shared data, I can envision it's getting more complicated.

 

[quangtran1]

Downloading.... It's like Christmas all over again. Thanks @Myself5!

 

[aholeinthewor1d]

Downloading.... It's like Christmas all over again. Thanks @Myself5!

What's up with the Gapps thing. Do we flash after or are they built in.

 

[quangtran1]

@Myself5, may I have 2 questions:
1) Which gApps should I download for the Pixel sailfish? I tried all combinations of ARM and ARM64, but they all failed to install due to "gApps size too large, try smaller gApps".
2) The ROM seems to get installed to the inactive slot on its own. If I set slot A to be active, Carbon is installed to B. Then I turned around and made B active on a different Pixel, it installed to A, and booted into A.
Thanks!

 

[TheNerdLLC]

This is rather nice to see. Thanks for your hard work.

 

[Myself5]

Looks amazing! I was never crazy about the AOSP look but I've gotten more used to it since the pixel is so close to being stock. Time to root and install TWRP finally. Love all the customization options especially the menu bar at the bottom.

Just curious what the Gapps issues are exactly because I've seen some other people mention them but didn't really go into detail.

Thanks!

They don't go into detail for a reason. The cause is, as far as I am informed, more or less unknown.
TWRP is suspected to be the cause at the moment, but I don't know much more either ATM. I'd, by guessing assume that it might be a mix of TWRP and the GApps installers that struggle with the AB system, but I don't know for sure.

I do know, that when installing a build with builtin GApps (we can't officially provide builds like this) its working, which is why I'll upload some unofficial builds with builtin Gapps until the issues are solved.

@Myself5, may I have 2 questions:
1) Which gApps should I download for the Pixel sailfish? I tried all combinations of ARM and ARM64, but they all failed to install due to "gApps size too large, try smaller gApps".
2) The ROM seems to get installed to the inactive slot on its own. If I set slot A to be active, Carbon is installed to B. Then I turned around and made B active on a different Pixel, it installed to A, and booted into A.
Thanks!

1) None ATM, even when hacking the Installer they seem to dissapear on boot. (See above for more Info).
2) The ROM installs to both slots, and then boots to one that wasnt selected previously, for whatever reason (might be TWRP related or Installer related (the pixel installer zips are really goofy) or even bootloader related, I can't tell for sure).



A Featurelist will be coming soon, please bear with us on that. We hard a very hard time even hitting our release deadline which was supposed to be the 31th of December 2016 but jenkins started to be very picky so all time to prepare threads on XDA and changelogs and stuff went down for jenkins. This thread for example is based on one of my old unofficial Note 10.1 threads, with very small changes. We will rework those later this week too. There was just no time at 4AM this morning to do so

Regards

 

[quangtran1]

They don't go into detail for a reason. The cause is, as far as I am informed, more or less unknown.
TWRP is suspected to be the cause at the moment, but I don't know much more either ATM. I'd, by guessing assume that it might be a mix of TWRP and the GApps installers that struggle with the AB system, but I don't know for sure.

I do know, that when installing a build with builtin GApps (we can't officially provide builds like this) its working, which is why I'll upload some unofficial builds with builtin Gapps until the issues are solved.



1) None ATM, even when hacking the Installer they seem to dissapear on boot. (See above for more Info).
2) The ROM installs to both slots, and then boots to one that wasnt selected previously, for whatever reason (might be TWRP related or Installer related (the pixel installer zips are really goofy) or even bootloader related, I can't tell for sure).



A Featurelist will be coming soon, please bear with us on that. We hard a very hard time even hitting our release deadline which was supposed to be the 31th of December 2016 but jenkins started to be very picky so all time to prepare threads on XDA and changelogs and stuff went down for jenkins. This thread for example is based on one of my old unofficial Note 10.1 threads, with very small changes. We will rework those later this week too. There was just no time at 4AM this morning to do so

Regards

Thank you!

 

[Simer03]

Carbon....No way

So we install it and then it boots the opposite slot? Is that what I'm understanding?

 

[fix-this!]

wow I thought carbon was dead. used to be my fav rom, thanks.

instructions on how to install?

 

[quangtran1]

Carbon....No way

So we install it and then it boots the opposite slot? Is that what I'm understanding?

It's installed in both slots. And yes, it boots into the slot that was not previously active. At this time, as the dev responded above, there's no GApps yet.

---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------

wow I thought carbon was dead. used to be my fav rom, thanks.

instructions on how to install?

You install it like you'd install any ROM in a recovery such as twrp. Then install gApps. There's no gApps available yet.

 

[dantexaiver]

So it installs to both slots does that mean it uses double storage space

 

[aholeinthewor1d]

So it installs to both slots does that mean it uses double storage space

It's the same setup you have now being stock. There are 2 of a few different folders including /system which is where the software is stored. No difference

 

[CZ Eddie]

It's good to see Carbon around!!!!
In anticipation of this becoming available for Marlin soon, I have a couple questions.

1) Does this have Slim Recents? I didn't see it listed on the features page.

2) I notice on the features webpage that it has light/dark theme options. Is it the one that can be set to automatically change? If so, does it have auto day/night Substratum support or does it only use the built in theme?

---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------

Pixel related info: Due to yet to be fixed issues, manually flashing GApps on the Pixel builds is not working on all ROMs. The GApps will be gone after booting. I'll might release an unofficial build with GApps included soon.

Yep, that's how DU and AOSiP are doing it for the moment.
Built-in. I didn't think it was possible to flash gapps at all, let alone have them install and then go away after reboot.

 

[Myself5]

It's good to see Carbon around!!!!
In anticipation of this becoming available for Marlin soon, I have a couple questions.

1) Does this have Slim Recents? I didn't see it listed on the features page.

2) I notice on the features webpage that it has light/dark theme options. Is it the one that can be set to automatically change? If so, does it have auto day/night Substratum support or does it only use the built in theme?

---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------



1) No.
2) The feature page is outdated, but will be updated later this day.
The ROM is having full substratum support, you only need to root and install substratum.

Yep, that's how DU and AOSiP are doing it for the moment.
Built-in. I didn't think it was possible to flash gapps at all, let alone have them install and then go away after reboot.

Will provide a build in the next days.
Flashing GApps "worked" after some dirty hacks to the installer Well... "working" as far as "it was there and then dissapeared after the boot" can be defined

 

[aholeinthewor1d]

Are there "legal" reasons Gapps can't be built in or something? Just curious because I've always wondered how it's OK to release some builds with them built in