yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
You folks are sure impatient. You can't run GApps without the Google framework and Google play services. Installing Play store alone doesn't make it work since it lacks the Google API to authenticate your Gmail account, hence the blank screen when Play is executed. In the past, there were 2 options. You could install a very tiny, basic Pico GApps just to get Google play services installed, then install other GApps. Or, Xposed had a Play Service replacement that you could use.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
GApps Build

The unofficial builds with builtin GApps will be here for the time being:

https://dl.myself5.de/sailfish/CarbonROM/

Enjoy :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Uh oh, better get your technical support staff ready. LOL!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] fix-this!:
so just do a full wipe in twrp and flash? may I ask if this is based on the newest security patch and build?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] peikojose:
Thanks! Can someone post some screenshots?

I'm still afraid of flashing because some people have had problems with the slot things.... I think that needs to be clear!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] fix-this!:
that and a list of what current features and whats not working.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] clockcycle:
Nice, good work, looking forward to the "merlin" version ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
It boots and works fine. I've followed same instructions as I used for another ROM.

Wipe, flash ROM, flash TWRP. Reboot and flash vendor. Done.

Backup your boot, system image, vendor image and data before wipe if you want to back easily to current setup.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
This is an unofficial build built just to get us something up and running. Anyone waiting for roms right now should have had time to understand what issues exist

Test it and see what it does. I'm happy with the intro first post and would prefer that they spend time working on the rom than the bio. They are working hard and ribbon and sparkles will be added to the descriptions when they csn
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Flashing is working fine, they all were just confused by the AB partitions :P

Working is everything. Camera is amazing (coming from a Sony device) and so on. Its a AOSP device running AOSP after all :P

*Marlin :P

I am thinking about taking responsibility for marlin builds as marlin and sailfish are unified anyways, but thats still a team decision to make. If we decide to do so, we'll for sure need someone to test before the release. If somebody is willing to test that, please PM me.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I keep getting vendor is out of date on boot. Which vendor file is correct one?

---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------

Here are a few screenshots of it's ok to post.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
the most recent vendor is the right one - nmf26q -

I am having an issue with losing recovery and SU - after flashing I don't have root or TWRP installed - and if I attempt to reflash twrp it doesnt work - I must have done something wrong - wonder if there are special instructions for flashing not outlined in the OP - something I may have missed? I get an error message when trying to open the link for the Carbon FAQ - so I am kind of at a loss here - any suggestions?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Works for me. Flash ROM, then right away flash TWRP. Boot at least once before flashing SuperSU.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
I was able to get root and and TWRP working on Carbon Here is what I did -

Flash Carbon Rom in TWRP

Immediately Reflash TWRP

Reboot to Recovery

Mount System

Advanced - File Manager - go to FSTAB file and delete

Flash Super SU (latest version - 2.79 I think)

reboot

profit

I did not come up with this solution - it was originanly outlined in another forum for Dirty Unicorns for Pixel - and apparently for the time being anyway - if you want root and TWRP after flashing Carbon you will need to follow those steps -

If I am wrong and there is a better way to do this please let me know.

Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Does the rom have Pulse or lockscreen weather?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I didn't see it. I think they are still adding features.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
SU 2.79 SR1 does not require the deletion of fstab. Actually, 2.78 didn't either, IF it were installed before a reboot. The fstab file is created after a twrp reboot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mocsab:
Thanks for the heads up - I must have missed that - I really appreciate the information. for what it's worth, I did originally try flashing SuperSU 2.79 without deleting the Fstab file - but when I did, flashing SuperSU just seemed to go too fast - it didn't take as many 'steps' as it normally does during a flash - so I thought maybe I needed to delete that file...But if you say so - I beleive you - I guess I did it just to be sure...now I know better - thanks! :)

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

I did not flash vendor and it booted fine - so that step may not be necessary on this rom...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] peikojose:
I am still worried, what happens if you switch slots in TWRP and you don't have a bootloader flashed in that slot? I saw reports of that happening.

---------- Post added at 01:31 PM ---------- Previous post was at 01:29 PM ----------

I want to flash a custom ROM to be able of hiding ths nav and status bar somehow, I fear Amoled burn! :S
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Well I guess you could just flash then switch slots and flash again. But if you have any big worries about flashing your phone then ROMs that are currently in early development may not be for you. Everything is still being worked out... Either keep data backed up or maybe just wait a while
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheNerdLLC:
Valid Point! When flashing ROMS in early Development, the key is to read the forum. When you read everything over, follow the correct steps, nothing less.

I learned this way back on the Samsung Fascinate. Been on here for years, since back then.

So, hope this helps! Remember, read first, then , keep this open on your CPU and always have repairable files for your phone accessible. That is why they say Flash At Your Own Risk!

Happy Flashing Everyone!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] FernBch:
Excellent Post.

Read and make sure you understand.

Have the correct tools (software) available and know how to use before you start.

Have factory image available just incase.

After that, in my experience, there's not much left to worry about and you can usually recover/restore if needed.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
why should you not have a bootloader flashed to a slot? what would be the reason to come up with the idea to delete the bootloader from one of the slots? its there by default, and should stay untouched anyways.

I might overexaggerate a bit here ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Turbojugend:
Thanks, can't wait to install this.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] AddictedToB3er:
Glad to see carbon back! Does this rom have a fully functional Google assistant? And fully recognized Google photos pixel benefits? I herd DU wasn't recognized for the Google photos original quality unlimited uploads as well as not functioning assistant.

Thanks in advance, I would flash and check myself but I just haven't had the time to play around quite yet.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
A big thing for me is if the "okay google" is working? As well, I wonder if the people having vendor issues are coming from the O build instead of the Q build therefore there is a vendor mismatch?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Turbojugend:
Just installed it and setting it up now. Set up ok google, but it doesn't stay working. It runs through the set up every time. Google photos detects it as a Pixel with full unlimited storage.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Now thats a feature I miss, weather on the lockscreen. i dont know why this went away?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pilotgav:
Whatcha doing with her
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
I think they were referring to the issues people have had with bricking there phones that hasn't been figured out yet and not slot questions with this ROM. Multiple people have managed to completely brick and no one has figured out how it happened yet so we don't really know what "not to do" when it comes to flashing things to the slots.

---------- Post added at 04:13 AM ---------- Previous post was at 04:08 AM ----------

There was lots of people that bricked and there's been lots of talk trying to figure it out but no one knows what exactly happened yet. Each person had a different scenario but somehow must have ended up deleting something important from the slots. They all had to get new phones because they couldn't even use fastboot or get to any kind of recovery or anything. So a lot of people are holding back for now hoping someone chimes in to clear up the slot stuff and explain what happened
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pWEN:
[MENTION=3816568]Myself5[/MENTION] You're probably aware, but just in case: the FAQ, screenshots, features, and team pages on your website lead to 404 errors.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Jup, the page is still going through the Nougat rework, and is not fully done yet, but thanks for pointing it out :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] derekr44:
Subbed. Keeping an eye on this one. Thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] je2854:
soooo, I am getting this...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Try to redownload
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ansontyl96:
try to redo factory reset in recovery, it works for me
[Google Pixel ROMs, Kernels, Recoveries, & Other De] je2854:
done it twice

---------- Post added at 02:40 PM ---------- Previous post was at 02:39 PM ----------

will try, thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Download the md5sum file too, and make TWRP verify the zip.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jorgen2009:
Today I successfully compiled carbonrom for the Pixel. It's compiled without GApps of course. Would including this commit be the only thing I would need for compiling a ROM with Gapps for the Pixel, even though the commit is for the Pixel XL?

https://review.carbonrom.org/#/c/635/
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Cannot wait until this ROM is ready with Gapps and pixel features (assistant, photos) fully functioning. Great stuff to look forward to!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Whats is the deal with the "okay Google" functionality being broken on every custom rom? Is it just something that is not fixable or just a feature that not big on the list?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
That commit, and the "1. Add the build system, and the wanted sources to your manifest." from here: https://github.com/opengapps/aosp_build#getting-started

The marlin tree is actually unified for sailfish and marlin. The sailfish tree on our git is just a dummy repo to pull in the marlin repo and to include carbon specific changes for sailfish (a small hack for roomservice was the alternative, but this seemed cleaner).

The commit is adding the OpenGApps defines to the device-common.mk, meaning its included for both devices, the Pixel as well as the Pixel XL ;) Hope that clears up some things.

Oh, also keep in mind that you need to manually add the vendor repo to your local_manifest, like so:

<project name="obsd39/proprietary_vendor_google" path="vendor/google" remote="gh" revision="cr-5.1" />

My unofficial build includes GApps and photos is reported to be working too already. Assistant is something we are looking into already :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
There's an enrollment process that Google uses to accept your trained commands. Looks like Google server is saying "I don't trust you and can't validate your device."

---------- Post added at 10:47 PM ---------- Previous post was at 10:46 PM ----------

There's an enrollment process that Google uses to accept your trained commands. Looks like Google server is saying "I don't trust you and can't validate your device."
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Makes sense,,,does it have something to do with build prop recognition?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Some apps/processes can be tricked with build.prop, many can't. Looks like OK Google requires more than just the device being seen as a Pixel. There have to be other signatures it's checking for, that custom ROMs can't provide. That said, [MENTION=3816568]Myself5[/MENTION], guess what, the beta version of the Google app just released yesterday makes OK Google work for any ROM now. I can't tell if the final updated version will restrict it again. To anyone else, you can join the Google beta program and enjoy this feature with your favorite ROM.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
OK google worked on nexus 5 customs ROMs when I was using them. Going to check out this beta though
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jorgen2009:
It sure did clear things up :). I made a successful clean build (not installed it yet as I'm on the January vendor already), but I get an error after 'make clobber' :

vendor/google/build/config.mk:41: *** GAPPS_VARIANT must be configured.
build/core/ninja.mk:163: recipe for target '/home/zeus/android/carbon/out/build-aosp_arm-clobber.ninja' failed
make: *** [/home/zeus/android/carbon/out/build-aosp_arm-clobber.ninja] Error 1

Any idea what I could do here, or is it best to completely delete the 'out' folder?

Thanks in advance and great job on the ROM!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Tracking the GApps repos is requiring the commit in the marlin repo, and also requires that sailfish/marlin got lunched.

your error is for the target aosp_arm, that means you didnt lunch before running the make commands ;)

P.S. We merged 7.1.1_r8 (NMF26U) tonight, so you might want to rebuild and then install.

Regards
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jorgen2009:
Thanks for your clarification again, I forgot to lunch before the make indeed. I never had to do that in pre-nougat times though :)

I saw the commit for 7.1.1_r8, but the version on my phone is NMF26V, not the U. I'm sure there's a valid reason why the 'older' U version was merged instead of the V version:)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Tempted to give this romantic a spin. I am rooted on stock desperately waiting to try a different romantic. Waiting for Lineage for the Pixel UT curious as to what features Car on brings
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Yes. According to Google (https://developers.google.com/android/images) NMF26V is for Europe/O2, whereas NMF26U is the "normal" Pixel release branch. This is why we went for V instead of U. I would assume that the V vendor.img wouldn't bringup any issues though.

Autocorrect got you hard on that one, hum? I suggest to try both and make your own decision. Any kind of opinion I give you wont be independent anyways ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] crossen0:
I'm in the US running the "V" variant?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Just downloaded and this still says "this feature is currently unavailable for this language"... Damn
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jorgen2009:
There are a lot of opinions as to why there are two versions. Purenexus is taking the 7.1.1_9 branch as their base for instance.

The Gapps included build I compiled today installed ok, but I had no sound and no mobile network. Probably while my vendor partition is different from the ROM, or maybe because the binaries from https://github.com/obsd39 are out of date (still the Q versions). What also seems strange is that the build includes both chrome and chromium (as well as webview). Seems a bit waste of space to me.

The ROM looked great though, or was my first encounter with carbon ROM, but certainly not my last
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ForevermanRGPC:
On AOSP 7.1.1 Roms I've always had to add

ro.opa.eligible_device=true to build prop to get Google assistant to work on none Pixel phones. Just a thought
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Myself5:
Yeah, we meanwhile decided to merge in r9 too, I'll do that tomorrow or later this day. Will also check about updating the binary repo. The double chromium/chrome is only because of the GApps commit (that will never make it into the build, for obvious reasons ;) )

https://review.carbonrom.org/#/c/780/ :P
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ForevermanRGPC:
Well, wasn't wrong[emoji12]. usually that little line gets missed a lot. You guys do great work, can't wait to give it a go
[Google Pixel ROMs, Kernels, Recoveries, & Other De] farfromovin:
I think it was the Galaxy Nexus or the Note 2 i last ran Carbon on but it was always just fast. Nice featureset with SPEED! The Pixel in stock form is no slouch though so it'll be very interesting to see if we can get a more fluid UX with maintaining stock stability as well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Did you happen to try this and it worked? And did you just use text editor and add it to the bottom of the build prop?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ForevermanRGPC:
They already have it in there per there git hub. I'm not running the ROM yet so don't have a build prop to look at.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bajasur:
FYI... OK Google is fixed in the Wednesday Google beta app update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aR_ChRiS:
How about the photos backup? Can we backup photos at full resolution on a custom rom now?

Another question, are we able to flash gapps on top or do we have to stick with built in gapps for now?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
Nice,,,def time to load up this rom if thats fixed thanks!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
If you're able to load the ROM with everything functioning (Gapps, assistant, photos, etc) definitely let us know!

[MENTION=3816568]Myself5[/MENTION] mentioned having a beta build with Gapps that is reported working. Link to that build here: https://dl.myself5.de/sailfish/CarbonROM
[Google Pixel ROMs, Kernels, Recoveries, & Other De] AddictedToB3er:
Are you talking about this build?

QUOTE=Myself5;70358755]The unofficial builds with builtin GApps will be here for the time being:

https://dl.myself5.de/sailfish/CarbonROM/

Enjoy :)[/QUOTE]
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
Anyone able to give input on Carbon vs Stock?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
[/QUOTE]

Yes, I edited my post with that link right when you replied ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Looks like PN will release today with gapps not built in, will the next release also not include gapps?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] devilsadidas:
Maybe plecebo maybe not but for me carbon seems to be speedier and to stay speedier after days usage. Also internet lags seem to have gone. The carbon custom settings are very nice... IMO Carbon > Stock
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ne0ns4l4m4nder:
Can I install this over latest update?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] aholeinthewor1d:
Curious why ROMs would be released without being able to flash Gapps as most people won't be able to use it then.

Also VERY confused on the story with the Gapps issue. Another dev here (I forget his name) made a thread the other day with instructions on how to get flashable Gapps working with any ROM. The thread was locked I guess because he didn't get permission from Beanstown.. but then Beanstown posted somewhere in another thread the same stuff and said any devs can feel free to use whatever it was that he figured out..

So I am lost. Seems like there is just a communication issue with all of this stuff. It's possible to flash Gapps with any ROM and the instructions were there.. but the thread was locked and other devs are still releasing them without the instructions for flashing Gapps which do work now
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Not sure what the issue with gapps is and I don't believe a ROM has been released without gapps included. PN will be the first I know of, that's why I was asking if this Roms next release will be the same.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
AOSP ROMs wouldn't include GApps built-in. GApps are not open source. Never were.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
Yeah I know that, I was referring to what the issue has been with AOSP Roms and gapps. Guess we'll find out soon!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
So flashed on the way to work today boote dup system was complaining about an outdated vendor image so the ui refused to load.

Got to work factory reset flashed latest factory image, installed Carbon , twrp and root and so far loving the feel good job guys
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Nice to hear a success story !
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ne0ns4l4m4nder:
OK so I just flashed latest Google factory firmware some how slot got switched to slot B, can I now install TWRP and just flash carbon?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Beans released Gapps today. Anyone tried to flash them with this ROM yet?

https://plus.google.com/+NathanBenis/posts/9knEpi9bJmp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
I flashed the ROM and got it to boot, but I still get the Vendor error. Not sure how or when I was supposed to flash that?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] dantexaiver:
1. FLash Latest Factory from Google

2. flash TWRP RC1 via fastboot and install the the twrp rc1 zip file, let it boot up complelty

3. Reboot into recovery flash carbon and supersu

4. ????????

5 PROFIT!!!!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] X04D:
Thanks for the response, but I tried:

1. fastboot boot twrp

2. installed latest OTA (nmf26u and nmf26v)

3. fastboot boot twrp

4. flash twrp

5. boot recovery

6. flash carbon

Still have vendor issue.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shindiggity:
So have you tried after you boot up rom and run through setup reboot in recovery and flash vendor again.