yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] jiv101:
So what's the process, fastboot flash vendor then flash rom then gapps?
[Nexus 6P Android Development] slaydog:
I wonder if you could restore a backup of just the vendor in recovery after flashing the ROM..?
[Nexus 6P Android Development] quantumqweef:
as in restoring a vender backup from stock/adb flash?
[Nexus 6P Android Development] slaydog:
Since you can use TWRP to backup/restore the Vendor image as part of a Nandroid backup, was wondering if it would work if you restored just the Vendor info from a backup with the same image (after deleting everything and flashing ROM/Gapps).

I might try just for fun, after I backup my current ROM. Probably won't work, I just like to try stuff, lol.

Not that it's a problem pushing with ADB, I just tend to mess with my phone the most when I'm away from home...
[Nexus 6P Android Development] joshndroid:
V3.1 is up on both sites... cheers
[Nexus 6P Android Development] DontPushButtons:
Sorry, I should've been a bit more specific. Vendor is untouched by ROM flashes for any of the 64bit devices since they split vendor into its own partition. It isn't necessary to flash vendor every ROM install. The only time you'll need to update or change it is when you're going forward or backward with major build versions; 29M to 29P, for example. Another time you could want to flash it again is if you leave some layers in /vendor/overlay and flash a ROM with the theme engine. Alternatively, you could also just mount vendor in twrp and use the file explorer to delete the overlay folder.

As for backing it up and restoring it, I've had mixed results, but mostly negative. So far as I've experienced, if you back up either the system image or vendor image in twrp, it'll cause a bootloop at the google logo when you restore the backup.

I think backing up the vendor partition is fine, although unnecessary as it goes largely untouched unless you use layers.

Hope that made some sense, I'm a bit sleep deprived presently.
[Nexus 6P Android Development] SpiritBreak3r:
[MENTION=4144316]joshndroid[/MENTION]

Network QS Tile on a single tap does not show the usual "Data Enable Switch w/ usage panel" instead it simply turns on/off data. Hard to notice if data is on.

Secondly, will it be possible to include a QS tile to switch Networks? (3g/2g/lte)
[Nexus 6P Android Development] :
I believe a LTE tile is already included!
[Nexus 6P Android Development] SpiritBreak3r:
Indeed, but implementing 2g/3g switch along with lte would be good. Since, I switch to 3g/lte only when im using data.
[Nexus 6P Android Development] :
OK. I've never really used that tile so I didn't know if it went to 3g/2g or not. My B.
[Nexus 6P Android Development] matt.parks:
I've only recently bought my 6P, I previously had the Nexus 5. In the latest CM13 nightlies for the Nexus 5, they've included qualcomm's snapdragon camera to replace the stock and you can see this in the CM13 changelog. These changes are present in the 6P changelog also, but the apk itself doesn't appear to be in the ROM.

Does anyone actually have this camera after flashing?
[Nexus 6P Android Development] adil7884:
discovered this by going into settings then sounds then advanced options then selecting the button in the back setting crashes,it is the same thing going on volume steps...
[Nexus 6P Android Development] dondavis007:
Listening in, what I've read it's a really good camera if all features is supported.

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Android Development] matt.parks:
Yeah it's a great camera, currently have it on my nexus 5 which is why I wondered if it was in the 6P :)
[Nexus 6P Android Development] joeydollar:
Practically Said
[Nexus 6P Android Development] slaydog:
I guess it has nothing to do with the Vendor image then, so not sure why flashing this ROM fails for so many of us...
[Nexus 6P Android Development] DontPushButtons:
That wasn't exactly the message I was trying to convey. If you haven't flashed the vendor IMAGE (not zip) from 29P yet, that could be the reason you can't boot this ROM.

I was just trying to give a more general understanding of why you don't need to flash a vendor every time you flash a ROM.

If you can't get it to boot, try flashing the 29P vendor.img through fastboot and let us know if that helps. Guessing gets us nowhere.
[Nexus 6P Android Development] jiv101:
Ive gotten the rom to boot, however after i flash Kylo kernel I'm again stuck at the google boot screen.
[Nexus 6P Android Development] joshndroid:
thank you

Guys, you must have FLASHED WITH FASTBOOT ONLY ATLEAST - it is exactly the same as CM-13.0 requirements

vendor.img

bootloader.img

(radio.img is in there as well)

form latest nexus firmware - https://dl.google.com/dl/android/aosp/angler-mmb29p-factory-25ed9560.tgz

All others

V3.2 is up both sites

Disclaimer - Don't try to use Viper4android, it is not for x64 bit device and will be removed for our device)
[Nexus 6P Android Development] DontPushButtons:
I was under the impression Kylo didn't always work on CM ROMs. I can't say I've ever tried it on CM to be honest, probably better off asking in the despair g+ community. Or using a CM kernel.
[Nexus 6P Android Development] dabug123:
I use kylo on aicp and RR works fine I believe both cm base
[Nexus 6P Android Development] DontPushButtons:
Looks like I was under a false impression then. Thanks for letting me know!
[Nexus 6P Android Development] kbapk:
In CM ROMS battery life is better than stock?
[Nexus 6P Android Development] joshndroid:
I'm going to say no on a direct comparison to bone stock rom.. But I have Bluetooth on and all the bells and whistles and have superb battery life anyway
[Nexus 6P Android Development] Upstreammiami:
I'm using this rom but I have have v4a working
[Nexus 6P Android Development] joshndroid:
Fresh install?

How did u install driver?

What su are u using?
[Nexus 6P Android Development] asem:
I'm on the latest vendor image and i'm able to flash all other ROMs with no problem. this one just won't load and gets stuck on the google logo. tried the latest 2 versions and the same problem.
[Nexus 6P Android Development] joshndroid:
Reflash vendor.img with fastboot only and it should be fixed.. Other roms especially those with layers will break it
[Nexus 6P Android Development] OmarUdave:
bluetooth work?
[Nexus 6P Android Development] PhilPan:
Does this rom of the 3mint battery mod built in?
[Nexus 6P Android Development] :
CM13 that doesn't force encrypt. I have foundeth the. Thanketh you op. ??✌

---------- Post added at 08:25 AM ---------- Previous post was at 08:18 AM ----------

Kylo works fine I too have used it quite a bit on aicp. Also Franco just pushed r8 with any kernel last night over on his thread so now his kernel can be used on CM. ?
[Nexus 6P Android Development] SpiritBreak3r:
つ ◕_◕ ༽つ 3G/2G tile つ ◕_◕ ༽つ
[Nexus 6P Android Development] Upstreammiami:
I'm. Meant to say I'm not using this rom lol... I just flashed the atoms zip file.
[Nexus 6P Android Development] PhilPan:
I heard 3minit battery is built in? Is this true? I got the app.

How do you enable.
[Nexus 6P Android Development] dlscott1111:
Keep getting device is corrupt message on boot. GRRRR!!! Fastboot Flashed the 29p vendor image. Am I missing something or is this normal Please help.
[Nexus 6P Android Development] jabreu203:
Normal
[Nexus 6P Android Development] :
I get it too. I believe it can be changed via boot.IMG or kernel... But its normal
[Nexus 6P Android Development] mindflayyer:
I'm experiencing some scattered screen tearing moving about the settings menu and while playing certain video formats. Anyone else?
[Nexus 6P Android Development] joshndroid:
seems to be a cm issue that has been present for a while....

device is corrupt message flashing up after google logo is because the device is NOT encrypted, selinux thinks the device has been tampered with (technically, which it has) so it throws that error. Please disregard it:good:
[Nexus 6P Android Development] joshndroid:
V3.3 is up on both sites
[Nexus 6P Android Development] dabug123:
Would it be possible to get rid of the crupt message ,this is only ROM left I experience it on..Thanks man either way nice work
[Nexus 6P Android Development] joshndroid:
see above again
[Nexus 6P Android Development] SpiritBreak3r:
Could the viper be an addon? I personally do not use it and wouldn't want it to be running the background since I route my audio via usb.
[Nexus 6P Android Development] dabug123:
Lol that might be possible right if not for fact I'm encrypted and get the error
[Nexus 6P Android Development] Nekromantik:
Ditto.

Should be optional.

Still laggy animations.

Have to turn them off for it to be smooth.
[Nexus 6P Android Development] btvolta:
Delete.
[Nexus 6P Android Development] PhilPan:
I see mention of 3minit battery in changelog, but not clear if it means it was taken out or put back in?

Can someone please answer me out there.
[Nexus 6P Android Development] joshndroid:
Viper should be removed from 64 bit devices from 3.3 anyway... If not just uninstall the apk and I'll look at the conditioner Tema put it to remove Viper for 64 bit devices
[Nexus 6P Android Development] :
[MENTION=4144316]joshndroid[/MENTION] just curious what kernel you use since your always bragging about performance! Thanks man!
[Nexus 6P Android Development] joshndroid:
Not once have a bragged about performance lol

I use stock kernel
[Nexus 6P Android Development] :
Not bragging, my fault. I meant you seem to have a solid experience. I had my governors messed up, mine is much snappier now. Thanks, and sorry for the bad word choice!
[Nexus 6P Android Development] PhilPan:
The assistance for this rom really sucks. I asked 3 separate times if the 3minit battery was in Rom or not. And never even was acknowledged.

Not that anyone cares but I'm outta here.
[Nexus 6P Android Development] DontPushButtons:
Next time try flashing the ROM and finding out if it has what you're looking for. In the time it took to blow your question out of proportion, you could have flashed the ROM and answered your own question. There are people floating around that help, when people have an actual problem.
[Nexus 6P Android Development] minhgi:
It is not that people don't acknowledge, they may not be using what you using. Why don't you try it for yourself and let us know of it instead. Always make a backup be trying something new.
[Nexus 6P Android Development] :
Please respect others and their time. Just because no one else has probably tried this out does not mean assistance is bad... Please feel free to try this for yourself.
[Nexus 6P Android Development] sherlock5545:
You know not everyone uses 3minit? I'm certainly not going to flash it for you just to make sure it works. If there's no answers, chances are no one that saw your question knows.

When asking questions for things that aren't specifically used by everyone, you should keep that in mind. Especially for things that aren't even in the ROM itself. If 3minit was a feature of the rom, I wouldn't mind testing it for you, but it's not.
[Nexus 6P Android Development] dondavis007:
Lol

Skickat från min iPhone med Tapatalk
[Nexus 6P Android Development] Ker~Man:
Poor, poor thing...
[Nexus 6P Android Development] Tung_meister:
What gapps are people using? I'm using the recommended opengapps but I don't get any screen off OK Google functionality, in settings it's only shown as available with screen on or device charging.
[Nexus 6P Android Development] dlscott1111:
Banks myself
[Nexus 6P Android Development] joshndroid:
V3.5 is up on both sites, cheers
[Nexus 6P Android Development] Tung_meister:
Is screen off "OK google" working for you?
[Nexus 6P Android Development] :
Not me either...
[Nexus 6P Android Development] joshndroid:
I never knew OK Google would work while phone was screen off lol...

Does viper for Android still get flashed? I think it might havr
[Nexus 6P Android Development] Tung_meister:
Yes it should work on the 6P, I've had it working fine on past custom ROMs with Open Gapps but it's not on this, I've just tried Banks with no success either - maybe it's an issue with the ROM?
[Nexus 6P Android Development] Poignant:
I'm thinking about using this rom coming from pure nexus 6.0.1 update, and I can confirm that screen off "ok google" works
[Nexus 6P Android Development] gd6noob:
Systemless root work on this rom?
[Nexus 6P Android Development] pittsburghfame:
my phone isnt booting after flashing the 0126 build. any ideas guys?
[Nexus 6P Android Development] Poignant:
same here ):
[Nexus 6P Android Development] gd6noob:
having issues with Viper4Android.. FCs
[Nexus 6P Android Development] Panzer87:
Mine didn't on first boot until I clean flashed ROM, then go to booloader and adb flash vendor.IMG, then gapps. Worked for me after those steps.
[Nexus 6P Android Development] pittsburghfame:
thanks but I already have the latest vendor and I reflashed it over for good measures and still getting the same issue.
[Nexus 6P Android Development] DontPushButtons:
Just to verify, you flashed the vendor image and not the zip?
[Nexus 6P Android Development] :
By adb^
[Nexus 6P Android Development] pittsburghfame:
via adb, if that's what you're asking, then yes.
[Nexus 6P Android Development] gd6noob:
adb or Fastboot?

I returned my phone back to stock flashing everything via fastboot then flashed Temasek, no issue..

Execpt the weather in cLock isnt working.. anyone else have this issue?
[Nexus 6P Android Development] joshndroid:
V3.6 is up both sites
[Nexus 6P Android Development] :
Fastboot eventually, adb to get there. And temasek said weather has been a wide cm issue. Should be fixed soon
[Nexus 6P Android Development] Tung_meister:
[MENTION=4144316]joshndroid[/MENTION] Any idea on the Ok google issue?
[Nexus 6P Android Development] nhugh406:
I cannot get the latest build to boot. Just fast book d back to stock 29p to start fresh. No dice. Thoughts??
[Nexus 6P Android Development] tibere86:
To save people some minor headaches, I can too confirm Kylo kernel does not boot on this v3.6 :(
[Nexus 6P Android Development] padlad:
Came from latest stock, advanced wiped everything except internal storage, booted up no problem.
[Nexus 6P Android Development] joshndroid:
Could be many things;

gapps package?

greenified google app?

xpose module interfering?

launcher overriding rom?

rom setting overriding launcher?

root disabling google auth for ok google?

dirty flash vs clean flash?

need to clear google app data?

that's all i can think of right now, some are more likely than others.
[Nexus 6P Android Development] Tung_meister:
Well I've tried a clean flash and multiple gapps packages, all of which result in OK google working fine on other ROMs with root. I haven't got xposed installed so I'd be leaning towards a ROM issue.
[Nexus 6P Android Development] danesusername:
Noticed some odd behavior in Status Bar settings on the newest build. When you enable Contextual Header, every time you switch between one of the three options it duplicates the settings list, for example there are two Clock sections, two General sections, etc. When you hit back and go back into the status bar settings it returns to normal. Might also happen on older versions, I normally don't touch the custom header setting. Doesn't have any negative impact but still pretty weird!
[Nexus 6P Android Development] joeydollar:
Has anybody ever notice that the Do Not Disturb button is not in the drop down menu
[Nexus 6P Android Development] :
You need to expand your QS panel, click edit tiles, click the plus icon, and add them all back!
[Nexus 6P Android Development] joeydollar:
Oh damn, wow. I wasn't aware of that feature that's awesome thanks a lot is a lot of things I'm still exploring
[Nexus 6P Android Development] :
No problem!

---------- Post added at 06:29 PM ---------- Previous post was at 05:47 PM ----------

[MENTION=4144316]joshndroid[/MENTION] what steps must be taken to flash the latest SuperSU? I've been running the latest ROM version for a day now. Can I just flash SuperSU and reboot or do I need to flash ROM again?
[Nexus 6P Android Development] joshndroid:
I always flash supersu along with rom
[Nexus 6P Android Development] joeydollar:
Me too.. Do it all at once. This is my first truly unlocked phone ever since the first droid came out. This is what community is all about
[Nexus 6P Android Development] Ker~Man:
A "ghost" 3.7 release. Nice!
[Nexus 6P Android Development] :
Has anyone figured out the OK Google thing? I have flashed other ROMs on my N6 (AOSP based, not CM) and my notifs and OK Google is all working flawless... May be BC of Google Apps or something else. Still trying to diagnose
[Nexus 6P Android Development] joshndroid:
V3.9 is up on basketbuild, romhut is being sucky
[Nexus 6P Android Development] djkinetic:
So I clean flashed the latest build, wouldnt boot, figured it was because of Vendor, so I fastboot flashed the latest Vendor from google's factory image, got it to boot, only issue is upon boot I get the Android System error, theres an internal problem with your device. You might want to upload a working Vendor specific for the rom. Flashing the vendor zip from the Benzo rom thread does not work either. Is anyone else getting this error with v3.9 and the latest vendor image?
[Nexus 6P Android Development] :
The latest February security update was just released. Temasek may have included that/or may not have depending on what your "latest vendor.IMG" it is your flashing. Try either the vendor for January or February, which ever you haven't tried... Check Temaseks changelog for info specifically
[Nexus 6P Android Development] djkinetic:
I flashed the vendor from MMB29Q so not sure what else would be later than that...might have to redownload the January one if it hasnt been updated.
[Nexus 6P Android Development] :
Try the vendor.IMG for January... What I'm saying is you may be a month off depending on when Temasek merged the security updates. Flashing vendor.IMG must go alongside the ROM, not the status of Google
[Nexus 6P Android Development] DontPushButtons:
Edit: after doing what I should've before I posted, looks like the build.prop is still displaying 29P. Vendor build.prop displays 29Q, that's why you get the prompt. You can update the prop in system manually and just match the build.fingerprint tag.
[Nexus 6P Android Development] djkinetic:
the MM29P vendor got rid of the error, looks like temasek didnt include the february vendor yet.
[Nexus 6P Android Development] DontPushButtons:
Check out my previous post, the build.prop(s) have a mismatch in the fingerprint.
[Nexus 6P Android Development] :
Exactly. Just gotta make sure you run the vendor.img of the ROM and not Google.
[Nexus 6P Android Development] djkinetic:
I knew how vendor and ROM worked, I has just assumed temasek had updated it is all.
[Nexus 6P Android Development] :
Check changelogs or ask before, especially when a patch is released. Saves you trouble! I always do that. Glad you are figured out though
[Nexus 6P Android Development] joshndroid:
Guys it seems every month we get the same response.. Stay on latest firmware..the reason why it occurs more frequent is because of the monthly security updates from Google back when nexus 9 came out this didn't occur so we could just set the fingerprint on major releases and forget. However this time round and for the foreseeable future the Fingerprint needs to be updated which it is awaiting approval via cm gerrit you won't have any issue because the rom has latest updates and the firmware complements that. If it's not merged by next build I'll pick it, but usually they are very quick with fingerprint merges

https://review.cyanogenmod.org/#/c/131147/

Edit - the device internal error on boot means absolutely nothing if you are on latest firmware and the rom source complements it, which cm does merge in latest source and in turn so does temasek for necessary repos. You only have an issue with that when rom source and firmware are mismatched and even then it's very minor u less your months different, at worst you will get instability and maybe a random reboot but seriously you guys have nothing to worry about, just stay on latest vendor, bootloader and radio (if applicable).
[Nexus 6P Android Development] :
Um... Well said!
[Nexus 6P Android Development] joshndroid:
Build V4.0 is up on basketbuild, thanks

edit - those of you on latest vendor image will get the internal device error, i completely forgot to pick the commit from gerrit, sorry about that

edit 2 - I have atleast mentioned on gerrit that the change is good and should be merged.
[Nexus 6P Android Development] joshndroid:
Well that did the trick a few hours after I commented on it, it has been merged =)
[Nexus 6P Android Development] fix-this!:
i really like this rom but the aokp animations are super choppy and gives lag. cant we just shut these off and use the standard animation from marshmallow? ive seen this mentioned a few times in the thread.
[Nexus 6P Android Development] Ker~Man:
So, I went from using this ROM for some time all the way to version 3.6, then wanted to check out Dirty Unicorns. Decided to come home to this ROM yesterday, and suddenly after reflashing, I can't get past the Google boot logo. I've tried all versions since (and including) 3.6 just for reference - same result. I'm on the latest Vendor image, and the newest TWRP, FYI. I'm at a complete loss. Only thing I've done since I've last used this ROM just fine is flashed / used DU for a few days. Everything else is the same since a few days ago when I was still in here. Please, please halp!
[Nexus 6P Android Development] Ker~Man:
Crickets? Love It!!!
[Nexus 6P Android Development] :
Patience is a virtue.
[Nexus 6P Android Development] Ker~Man:
I was just playing, man. Is there any assistance with my problem you're offering?
[Nexus 6P Android Development] :
Issues such as these have been discussed many times before, not sure if they well help though... Never has happened to me, just make sure the vendor.img is the same as the ROM and clean flash with proper Gapps.
[Nexus 6P Android Development] Ker~Man:
I've seen all the vendor image discussion. I flashed the MMB29Q vendor image which I found coincidentally on DU's G+ page. Someone had created it into a recovery-flashable zip. So, that's the one I'm currently on. That couldn't be incompatible with other ROMs (i.e. this one) could it?
[Nexus 6P Android Development] :
It seems for this ROM you must flash the vendor.img via fastboot, as zips have had problems. Always try to go completely stock when diagnosing a ROM problem. ROMs are different. Try flashing vendor.img via fastboot.
[Nexus 6P Android Development] Magnetox:
what's the difference between this and jgcaaps builds in original android development?
[Nexus 6P Android Development] :
You tell me! I have no idea! Never heard of his builds.
[Nexus 6P Android Development] Magnetox:
I think this version has more features where jgcaaps builds are simply pure CM13
[Nexus 6P Android Development] Ker~Man:
I'll try and report back. Thanks!
[Nexus 6P Android Development] :
Let me know.
[Nexus 6P Android Development] joshndroid:
V4.1 is up on basketbuild. Thanks
[Nexus 6P Android Development] Sblast:
Thanks Josh!
[Nexus 6P Android Development] Ker~Man:
Fastboot'ing it worked. Thanks!
[Nexus 6P Android Development] :
Knew it would. Welcome.
[Nexus 6P Android Development] joshndroid:
V4.2 is up on basketbuild
[Nexus 6P Android Development] shag_on_e:
Yayah, think I got first download! Seems fresh so far...two builds back I noticed live lockscreen seemed to cause a memory leak for me, or something similar. I got major lag until I turned it off. Definitely not a deal breaker, though it is pretty cool.
[Nexus 6P Android Development] Upstreammiami:
hey guys i came from aosip but when i flashed the rom it only boot to the google screen ....how can i fix this ?

---------- Post added at 09:36 AM ---------- Previous post was at 09:29 AM ----------

ok so i flash xelement and its booting now
[Nexus 6P Android Development] buddwm:
The latest version of this rom does not appear to be rooted? I had to manually flash SuperSU to get any kind of root. Anyone else get the same issue?
[Nexus 6P Android Development] DontPushButtons:
You have to turn on root access in developer settings to use the built in root.