yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] 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
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
This is want I do. Backup boot, system image, vendor image, and data in TWRP.

Then wipe and flash a ROM. .If you want to go back to stock config just restore your TWRP backup.

---------- Post added at 10:20 PM ---------- Previous post was at 10:19 PM ----------

Yeah I've heard of that but haven't bothered with it just yet. I'm fine with restoring. I also have TiBu backup.

Multiple user might be more useful for dual booting. There are a couple of issues still with that and it doesn't interest me too much.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Understood, but could I restore my current data while on carbon without reverting to stock? In essence, run my current setup of apps and such, but in carbon.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
That could mess with things. Do a full backup in twrp tor backups sake but for your data and apps use titanium backup batch backup or something like it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Clearification

So, after more testing and after talking to [MENTION=2385005]invisiblek[/MENTION] and [MENTION=4433359]spaceman860[/MENTION] it turns out that I was wrong. Carbon is not flashing to both slots. The reasons I was thinking it does flash to both slots was because during my initial testing I flashed the same zip twice, which was the cause that it got flashed to A and B.

So, Carbon is doing the same as every other ROM, flashes to the slot that you are currently not on and then boots to that.

FYI: Currently doing the last tests for NMF26V, weekly are starting soon.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
If I created a titanium backup of 'all user apps + system data', then factory reset, flashed carbon+TWRP+SuperSU, could I then restore my titanium backup? Giving me my exact current setup but with carbon instead of stock rom?

Obviously assuming I exported my titanium backup before performing factory reset.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Yes you can use TiBu to do this. What I did was restored all user apps. Didn't try system data. I did a Google cloud restore for most of that stuff.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Is there a risk of restoring system data with TiBu instead of relying on Google cloud?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I don't think there is. Other have done it, I haven't tried it yet. TiBu will ask you to change device ID on first startup. Select yes.

Also wiping data in TWRP does not wipe your internal storage. Including TiBu backup. You have to select to wipe internal as storage. Don't do that though.

Flashall will wipe this though.

---------- Post added at 11:32 PM ---------- Previous post was at 11:29 PM ----------

Sent you a pm.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
To be clear: to flash carbon, we need to factory reset? Which will erase internal storage. Or do we just need to wipe data in TWRP, which keeps internal storage?

Also, did not receive pm.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
You just need to wipe data in TWRP. It's the same as factory reset except it preserves your storage.

Looks like it sent to your Tapatalk account. Ah well. Just had a suggestion.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
I wouldnt do a factory reset. Id wipe everything but internal storage. If you dont wipe the system and are going from stock to aosp you will most likely run into issues. Restoring certain aspects of stock system to aosp you may also run into issues. Letting google do its cloud restore is probably the safest way for that stuff.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jorgen2009:
Factory reset doesn't wipe your internal storage, it'll wipe your userdata partition (and probably cache too, but I'm not 100% sure on that). Anyway, your internal storage, where all your photo's are stored among other things will remain intact with a factory reset in twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Atemi1337:
I just tried to check the feature list and change log, I'm only getting 404 errors. Anyone else having the same issue?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Yup
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Well this is bizarre rebooted and no longer have root or Su installed boots me to stock recovery. How do I make tarp and Su permanent
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
If for some reason you're reflashing the same build restoring system data should not be an issue. When flashing a later version it could pose problems. Since it is possible system apps can be updated it's normally best to let them create a new data profile.

Just my humble opinion based on past experience.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JGoldz75:
How's the battery on this ROM compared to stock?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheNerdLLC:
New build is live, who has flashed it, any issues?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
I did :D Works fine, GApps flashing is still broken. (Working build with GApps is in the know folder.)

HOWEVER: After talking to some people, the next build is going to include the GApps fixed kernel.

Thanks to [MENTION=912474]Dees_Troy[/MENTION] for pointing that out ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] piperx:
You should try it yourself and compare, everyones usage is different
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I only restore user apps.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
I've skimmed through this but didn't see it mentioned, can anyone tell me if V4 is working on this? And also is Substratum working?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
May I ask what V4 is?

Substratum (OMS7) is fully working. Just root the phone and install the app from the playstore :)

BTW, next weekly will have the GApps fix included, I'm currently preparing everything :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
I'm sorry viper audio. And thank you!

---------- Post added at 11:17 PM ---------- Previous post was at 11:12 PM ----------

One more quick question. I've got pure nexus on slot B when I install this according to my readings this will install on slot A . does that mean if later on this evening I can boot back into slot a? Or did I misunderstand
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Could be worth a try. I didnt test that yet personally TBH. Be sure to boot in the PureNexus Slot, cause Carbon will install to the opposite slot. Then it might work. Not sure how the apps will behave though.

Try and report back :)

regards
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
Modded V4a is excellent

https://xdaforums.com/pixel/themes/mod-wetaaudio-t3490886/post69387326

Dual booting two different roms will not work with the shared user partition. You have to separately back up data on both roms. Reflash the roms to both slots. When you switch roms you would have to wipe data, switch slots and restore your backup. Doesn't seem practical.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
Perfect! Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] adinkwok:
Hey guys, I'm one of the core developers of CarbonROM...

...and there is something I would like to address:

I would like to keep our threads clean, and strictly about development and/or related topics. XDA is the place to be helping one another, sharing ideas, bringing each other up in this developer community through contributions. Because of the impulse of certain users, I want to follow a strict policy for postings.

The general idea of what should/should not be posted here is outlined in the XDA forum rules.

Things like...

...should not be posted here.

Things like...

...are welcomed with open arms (and maybe even kisses, too!)

The only off-topic posts that may happen here may come from a CarbonROM core developer announcing or asking for a certain opinion on XXX feature. Thanks for understanding, this is the way development threads were meant to be in these forums. I invite everyone to stay vigilant to report posts that do not follow the summary by MikeChannon in the XDA rules about what should not be posted. Do not engage users if they don't follow the XDA rules, Forum Moderators exist for the purpose of handling such users ;). Long live the report button!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spicemaster:
Download links for sailfish not working?? i cannot download any of the 2 builds available.

please help.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
check https://basketbuild.com/devs/CarbonROM for now. I'll let our server master know about the issues.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Protibus:
Am I right in assuming Gapps are included in the ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
On the weekly I'm not 100% but i didn't think it was since the file size is so small. It is an unofficial release that had them built in. I downloaded the weekly Friday but didn't install because he said the next one will have the gapps install issue fixed and I am assuming a weekly would release soonish.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
New Weeklies are up already, check https://basketbuild.com/devs/CarbonROM/. The verity fix is included in there too. (https://github.com/CarbonROM/androi...mmit/6620c0c51d410721af8bad792581fd6663bca72a)

What you need to take care of though is this:

The ROM flashes to the opposite slot, as discussed before. The only GApps that work with the Pixel ATM ( [MENTION=4395895]BeansTown106[/MENTION]s Dynamic GApps ) however flash to the currently ACTIVE slot.

This means, in a scenario where you are on Slot A ATM: Carbon Flashes to SLOT B. When you reboot after flashing the ROM will boot to slot B and is booting Carbon. HOWEVER. The GApps flash to your currently active slot. This means, when you are currently on slot A and flash the GApps, they will be flashed to slot A (keep in mind, your ROM is flashed to slot B). Hence you won't have GApps on the ROM when booting. The simple solution (until the GApps zip is fixed) is:

1) Flash Carbon

2) Flash the twrp.zip

3) Reboot -> Recovery

4) Flash GApps (cause now you are on the proper slot)

5) Reboot to ROM, enjoy GApps.

6 (optional)) Reboot to Recovery again and flash whatever you desire, like SuperSU.

This counts for every ROM btw, as thats the default behaviour of the new payload A/B flashing system for the Pixels. [MENTION=4395895]BeansTown106[/MENTION] based on that the commit message in the commit you linked doesn't look right :silly:

The get.carbon page ATM needs to get manually updated, we'll take care of that later.

Server infrastructure is still a WIP as some might see, but I hope you'll bear with us, as things are progressing every day. Just mainly on the unseen end ATM (like CAF Support is about to be done :) ).

Regards
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Im getting all kinds of google play services errors. Tried fresh installs on both a and b. Booted up ROM then rebooted to recovery to install gapps and also just rebooting recovery.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
You're installation went fine, but the Google play service has some issues for some reasons.

Settings -> Apps -> Google Play Services -> Permissions and grant the app all permissions. For some reason they are not enabled by default. Got to figure out if that a GApps or a ROM issue still.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
The pixel is going through the same issues the nexus 5 had when nougat first came out... I will try that. Thank you

edit: now when i get it to boot up i haved no keyboard but voice typing and there is no way it can do my passwords... gonna try the other version of gapps

Edit2: not sure what was going on. Installed to other slot again and its all set up and good. Even did the cloud backup fine.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Thats actually useful information though, because now we know where to look for a fix ;D

If you could provide some more information about the Nexus 5 issues like when it got fixed (maybe even on what ROM) I'd be glad to review the fixes and see if we can do something about them on the Pixel.

I am almost suspecting a ROM/GApps problem though, because we recently got a report about the same issue with the same GApps/ROM combinition on the Nexus 6p. Maybe we missed some permissioning.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
I can look but am not sure. I broke my n5 before a fix and picked up a galaxy s6 that was way behind 7.0 lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quinejh:
This is a fantastic ROM. But I'm curious if someone can recommend a way or an app then can hide the nav bar. I use pie but really like the full screen. Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
the 01-07-2017 release is throwing an error in twrp "meta-int/com/global...etc" couldn't be found in the zip file. downloaded it twice. am I doing something wrong?!?!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
What steps are you taking during flashing?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
Fastboot oem unlock

Boot to homescreen

Fastboot boot TWRP.img

Then flash TWRP as IMG in TWRP to make it stick

Then SuperSU

Boot to home screen again

Go to recovery

Flash Carbon zip.

Then it throws meta INF error. Tried on 01/01, 01/07 and 01/15. Same thing

---------- Post added at 05:51 AM ---------- Previous post was at 05:48 AM ----------

I've installed the pure Nexus rom before. After some help, I got it to work. But this one is giving me trouble
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Turbojugend:
When I got this error with other ROMs, it was because I needed to update my ADB and fastboot files to the latest versions.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
Very odd. I had just deleted and redownloaded them. But that doesn't make sense as I was getting error in twrp

---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------

oh boy..... was I suppose to unzip and flash?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Well without knowing what you did no one can actual help. So I guess my answer is I don't know.

---------- Post added at 01:25 PM ---------- Previous post was at 01:25 PM ----------

No... Do not unzip. TWRP flashes the zip
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ej_424:
Can someone comment on the camera quality compared to stock?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Turbojugend:
I don't need help, I was telling them how to fix the issue they are having. I had outdated ADB and fastboot files, I updated to the latest ones in the Android SDK, and everything worked fine after that.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] abieofficial:
Hey [MENTION=3184218]devilsadidas[/MENTION] & [MENTION=6923892]trentag1988[/MENTION] I just solved it. Change your TWRP to https://dl.twrp.me/sailfish/twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip

My Sailfish just boot very well. I hope change to this Custom Rom can fix my DND. When I was Stock rom, I cant place and receive a call. The DND bug always annoying me :(
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
That is the version I have been on. Not sure of the issues you faced with stock as I had none. But havnt been on stock for some time. Hope this ROM works out for you.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] abieofficial:
Yeah but it not affect my Sailfish. If I receive and make a call, my Sailfish just freeze at little time. Still not work at all. I'm so unlucky bought expensive 128Gb phone for $896.79 with fault product.

Damn Google or HTC? HTC for manufacture?

Sorry for my bad english
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Well if you bought new its under warranty.... Any product no matter the expense will have some that are just bad, that's what warranties are for. Don't be mad at google/HTC. All phones have a few that won't work
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Just a headsup: If someone experiences any issues on the upcoming Weekly builds (Server issues delay them ATM), please try a clean install.

During the CAF bringup I came across situations where the S810 Z5 was a LOT smoother than my S821 Pixel. My research delivered some potential issues with the devicetrees, and testing the ROM the device trees originated from delivered the same results. When both devices would run a clean install, the Z5 was performing a lot better in terms of opening the Settings App for example. I did some further tests then, and eventually rebased the devicetrees on top of the new LineageOS trees.

After above a week of testing now I can say the result is a LOT more satisfying, and the overall experience is in the way I expect my Pixel to behave. No more microstuttering whatsoever.

As a result of that, the zip size decreased by ~60MB (sailfish builds are now ~306MB), the UI performance improved and at the same time the batterylife stayed the same (might have even improved slightly but that could be caused by my recent theme changes).

Just thought I might "warn" you upfront in case someone is experiencing issues. There shouldnt be any, but I did a cleanflash for the builds too (cause I messed up my data with an feature testbuild at the same time), so I can not say if a dirtyflash is going to work or not.

Regards,
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
This is probably a silly question, but on clean flash, you mean wiping system and data and just flashing carbon ROM? Don't reinstall on top of stock ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheNerdLLC:
[MENTION=3816568]Myself5[/MENTION] Does the latest weekly come with Gapps?

Also, if coming from purenexus do you just wipe and install?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jasonsamms666:
Wipe data, cache, and system then install the ROM, vendor, and TWRP installer. Reboot recovery and install Gapps.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trentag1988:
Ohhhh snap. Okay ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
No GApps as the install has been fixed.

Coming from PN cleanflash as per:

I dont see the need to always flash the newest vendor.img though, just update it on both slots when a new one comes out.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jasonsamms666:
I just threw that in there in case he hasn't installed it yet.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thebigdonny:
I was just stalking checking the CarbonROM download page and saw a weekly posted. Decided to download it and try it out, but I get an error trying to flash it. Only then did I realize I was looking at all devices and the weekly build posted was for my old Shamu :silly:

Looks like there's a couple builds now, so does that mean the build server is back to operational? If so, that's exciting!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
You mean something like the pic in the attachment?

I dirtyfixed it for now, installed Linux, wasnt able to get Windows back yet, but thats WIP. Stopped that for now so we can get the weeklies done.

I wiped my ccache during the tests for fixing the build error on jekins, so each build on there will take ~35min. Leo and shamu are done, after that sailfish, shieldtablet, angler, sirius, marlin, mako, hammerhead and aries will follow (in that order).

We also managed to automate get.carbon using jenkins now, so as soon as the builds are uploaded they will now appear on https://get.carbonrom.org :)

Thanks to everyone for the ongoing patience and sorry for the delay :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thebigdonny:
Sweet! I gotta say, I'm a fan of the build order at this moment in time :good:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thebigdonny:
Got the latest weekly downloaded and installed. Little hiccup with no keyboard on fresh install, but flashed again and now getting things set up again. Also had to grab NOF26W vendor image rather than NOF26V.

[MENTION=3816568]Myself5[/MENTION] Are there any plans to make WiFi Calling work? Not seeing the option to enable it anywhere. Everything that is there is great so far, so thanks for all of your hard work!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Oh, yeah. Builds are using the NOF26W files. We follow the Pixel branch on the ROM base and are always using the newest one, and as it would be stupid to use a different branch on the Pixel device trees then, thats why the more "uncommon" versions are used.

Thats in line with the branch and revision decision Lineage does BTW :)

I don't know anything about WiFi calling TBH, thats something I would need to look into. With that said, I don't know if it would be possible to add either. I'll take a look at it when there is time, I promise :P If there is some other ROMs that _do_ feature that, please let me know. That would be something to start with then :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] thebigdonny:
No worries on the vendor thing, figured there were reasons ;)

WiFi calling is in Pure Nexus, Dirty Unicorns, and OctOS. The difference is that they're all AOSP based I think rather than Lineage. With that said, I think OctOS is rebasing and said they'd still have WiFi calling on Lineage base. I don't know a lot about the "behind the scenes" so hopefully any of this makes sense :good:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Oh Nice. I'll take a look at those then.

Carbon is not Lineage based either, we're just using the Lineage device trees as the previous ones kept on throwing issues ;)

I am in contact with some Lineage Devs for various things, like the Z5 bringup or some CAF bringup related thing for Carbon, hence there might be references to Lineage decisions here and there :P
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GohanBurner:
Great ROM love it!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] uodii:
[MENTION=3816568]Myself5[/MENTION] Is there a difference between the 2/16 weekly and the unofficial 2/18 build?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] MpandAUS:
Wiped and factory resetted, installed the ROM, twrp then the latest supersu, it booted and google installation came up however I didn't want to install all the apps over again so i went restored my data partition only via twrp, it booted and worked. I put my sim pin in, worked but when I put device pin in, it won't work. It says device locked after the device restarts. Any idea on how to fix this?? :(
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Did TWRP ask for a device encryption PIN when you started it? It sometimes doesn't for me, which seems to be responsible for things like that. Reboot to recovery, make sure it asks for the PIN and the restore your data again.

It's totally not recommend doing that BTW, and is known to cause multiple issues across custom ROMs, so I'd suggest a clean flash when coming from a different ROM nonetheless ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Yes

Edit: Seeing your other posts in the ElementalX thread you probably don't care about it and just want to push your postcount though, lol.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sharingspider:
Nice Work Dev. Gonna Try it Soon. Downloading :)