yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] GrayFox814:
Thanks for the kind words and assistance gents. I did search. Found 3 posts, two of which said nvm i fixed it and didn't say how. The other said to flash cm, boot and then flash gapps, that didn't work for me. If someone could point me in the right direction I'd really appreciate it.

Found one more post that didn't show up in the search, but again not helpful for me. I'll keep wiping and reflashing for now. I went through the welcome screens without flashing gapps and the problem still happened so idk whats going on.
[Nexus 6P Original Android Development] boxguy1:
I will give it try thanks

---------- Post added at 02:24 AM ---------- Previous post was at 02:22 AM ----------

Oops ðŸ˜… I guess I should have read the first page before commenting thanks for the help guys
[Nexus 6P Original Android Development] Enhanced:
If you go between the screens quickly, you'll see a skip button. Try hitting it.

If not, don't connect to WiFi initially.
[Nexus 6P Original Android Development] GrayFox814:
THANK YOU
[Nexus 6P Original Android Development] wrkerr:
Thanks.

Any tips on how to make a custom link to it? I'm not seeing that functionality in ADW or Nova.
[Nexus 6P Original Android Development] Sheetzie03:
There's a build prop edit that disables noise cancelling mic and it fix the echoing issue
[Nexus 6P Original Android Development] ChemoNL:
For Nova

Long press home screen

Press widgets

Select activities under Nova Launcher

Browse to the app

Select Main activity

ADW I don't know
[Nexus 6P Original Android Development] D@rekills4:
Check the screenshot I have attached.

If anyone has another phone please compare the colours of your screen and Nexus 6P's. I am running the 9 December build.

The colours seem way more saturated than what they should be.
[Nexus 6P Original Android Development] Dark_Eyes_:
Still not working, logcat error is : cpe_reg_sm: ERROR, SNDRV_LSM_REG_SND_MODEL_V2 failed, status=1

The switch toggles back to off after 2-3 seconds.
[Nexus 6P Original Android Development] tydiamond11:
It just crashes for me after going through setup
[Nexus 6P Original Android Development] hanschke:
anyone got the same problem that after a clear installation the home button and right button dont work? and why is the setup bug not fixed yet :confused:
[Nexus 6P Original Android Development] D@rekills4:
1. No, I don't think so.

2. Probably because the developers don't know what is causing it. If they knew, they would have fixed it.
[Nexus 6P Original Android Development] zain0300:
Did you try toggling "Picture Color Mode" on and off in Developer Options?
[Nexus 6P Original Android Development] cwassman:
Thanks for the guidance regarding the echo.... changing persist.audio.fluence.voicecall to FALSE does help sound quality when

handset

calls are made, but I don't notice any positive change when using

speakerphone

. :(
[Nexus 6P Original Android Development] Sheetzie03:
This ' might ' help, found it on XDA, fishable zip, it's worth a shot
[Nexus 6P Original Android Development] g_kos:
Happened to me as well.

Go back couple of screens, and disconnect from the WiFi. then proceed with installation and you will not be stuck at this step.
[Nexus 6P Original Android Development] razorloves:
It's just the LiveDisplay feature in cm. It auto turns on at night. You can turn it off or adjust the color temps it auto changes to. It's in settings - display.
[Nexus 6P Original Android Development] D@rekills4:
@razorloves and @sam3000,

My apologies, the first one is a bug on all CyanogenMod 14.1 it seems.

I have experienced it on 3 devices. Nexus 6P, Moto G4 Plus and Samsung Galaxy Note (GT-N7000).

That made the saturation way too less, the display seems whitish. Plus, that option is not enabled on any of the other phones.

But after turning off this option, I had to turn the display off and on again for getting it to work, my 6P showed me the correct colours (this also happens when you turn any other colour related options on and off).

But it lasts only a few minutes and goes back to the saturated colours soon enough.

No, I have disabled all those features.

The colours are more saturated. Especially red looks brown on my Nexus 6P.

As @zain0300 suggested above, to turn on sRGB mode, it made the display whitish, not the original colour.

So I turned off sRGB mode and the display showed me the correct colours. This also happens when I change any other colour related settings. But a few minutes later or after rebooting the phone the display goes back to the saturated colours.

If I take a screenshot and put it on another devices the correct colours show up. This is a problem at the output, no idea what is causing it.

And trust me, this is real.

I am colourblind so I went and asked my friends the difference in colours of my N7000 and Nexus 6P (since both have AMOLED displays and running CM14.1) and they clearly told me that there is a visible difference, all colours and more saturated and the red pretty much looks like brown on the 6P.

I am on the December 9 nightly, the first 7.1.1 build. (Clean install)

And another bug maybe? The Google Voice typing icon is not appearing on Google Keyboard. Not sure if this is a CM related bug though. Any other Google Keyboard users here?

It works fine on AOSP keyboard.
[Nexus 6P Original Android Development] razorloves:
You can't complain about some color problem and then make that statement and expect us to listen. lol. jk

But anyways, i haven't seen this issue so idk. One thing I do want to point out. Make sure you're on new vendor, bootloader and radio linked in first post. Also, you should update to new nightly. There were several mismerges with 7.1.1 that were fixed and are still being fixed, after your old nightly. And I hope you're not reporting this issue while using custom kernel or some kernel hacker.
[Nexus 6P Original Android Development] D@rekills4:
I just want to help you fix bugs, this is the most I can do since I don't have enough knowledge about building CM myself.

Yes, I am on the new vendor, bootloader and radio, I flashed the latest 7.1.1 stock ROM before coming to CM14.1

No, I am not using a custom kernel or any kernel hacker, it's pure CM14.1.

Maybe I will try updating to the latest nightly.
[Nexus 6P Original Android Development] D@rekills4:
Well, I updated it but the issue still seems to be there.

One thing though, if I disable and enable sRGB once, the real colours come back until I reboot the device so that's there as a temporary workaround.

Thanks razorloves.

Edit:

The Live Wallpaper bug is still there, don't know how a certain component within a Live Wallpaper can get bugged because of a ROM. :laugh:
[Nexus 6P Original Android Development] TokedUp:
What music player comes with 14.1?
[Nexus 6P Original Android Development] Marcuss4:
Is there a list with all known bugs?
[Nexus 6P Original Android Development] ariefabuzaky:
Its most completely stable
[Nexus 6P Original Android Development] tdg2k15:
Been using flash kernel with 11/11 build. No issues yet.
[Nexus 6P Original Android Development] mhsbrian:
I indeed did try but had some random reboots. I thought maybe they were occurring when I tinkering with account related settings but also happened when I was in the gallery scrolling photos. I had no other mods, didn't even have my apps restored yet either, so I figured give these builds a few more days.
[Nexus 6P Original Android Development] Jammol:
Please use the Nano version of opengapps.

I used the aroma version and only keyboard had issues for me. I reinstalled from scratch and didn't select it.
[Nexus 6P Original Android Development] infus38:
Hello i would like to know how to get the notification or phone from the ROM stock 7.1.1 on cyenogenmod thanks in advance
[Nexus 6P Original Android Development] DaReDeViL:
Stock gallery crashes on me even with stock kernel, so it's not related to kernel ...
[Nexus 6P Original Android Development] tdg2k15:
Agree, I noticed it myself this morning. So I thought it was cause of the flash kernel. So I flashed CM official boot.img and still causes my phone to freeze and reboot.
[Nexus 6P Original Android Development] antmunny:
weird...i'm 100% stock cm14.1 clean flashed with open gapps pico.

gallery was fine
[Nexus 6P Original Android Development] tydiamond11:
Same here
[Nexus 6P Original Android Development] DaReDeViL:
I'm using nano gapps, maybe that's the reason ...
[Nexus 6P Original Android Development] tydiamond11:
I am using stock gapps lol but
[Nexus 6P Original Android Development] Breezer23:
Bizarre. With latest Vendor image, nightly and the latest Nano GAPPS I can't get past the set up screen. The ROM will have me connect to WiFi then it goes through an infinite loop of trying to restore from another android device. I can't even complete setup lol.

*EDIT* Nevermind, read the post on page 1. Ignore this.
[Nexus 6P Original Android Development] sam3000:
What does your settings -> about -> kernel version say ?

Gallery crashes (and device restart) were believed to be fixed by these patches. They fixed it for myself and various other people confirmed the same.

If it's just gallery crashing (and not the device restarting), could you please post a logcat ?
[Nexus 6P Original Android Development] DaReDeViL:
Oh sorry, I just restored a twrp backup for some 7.1.1 kernel tweaking ...

Anyway, the problem I was facing was Gallery crash followed by a reboot. It happens also after playing a video in whatsapp ! Be it on stock cm kernel or googymax kernel.

I really need to have a dual boot setup to be able to help more in both worlds ;)
[Nexus 6P Original Android Development] sam3000:
I can't repro the crashes. Does gallery work sometimes or does it always cause a device reboot ? Very roughly, how many images and videos do you have in media ?

Only interested in behaviour on stock cm because we have no control over 3rd party kernels.

Thanks
[Nexus 6P Original Android Development] tydiamond11:
So the issue for me is that whenever i install say a system font or a pixel type boot animation my phone gets boot loop that is the only thing that is really bothering me about cm14.1 right now. I only know of the fix of dirty flashing the newest build over it and that seems to fix it. But than some apps crash and i have to uninstall them and reinstall them. lol just some issues...

---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------

One more thing is the phones sounds come through and Bluetooth is connected to things like my watch and stuff but it is still stuck on the boot animation.
[Nexus 6P Original Android Development] ps000000:
I will try clean again and pico.

nano make stock gallery reboot.
[Nexus 6P Original Android Development] info[]box1:
That's for stock builds.
[Nexus 6P Original Android Development] razorloves:
i've been using 11 nov nano and gallery is working fine for me.
[Nexus 6P Original Android Development] Jammol:
Aroma works great as well if anyone is interested. Just don't select the Google keyboard. Install from play store if it's needed. Also if anyone is interested, I have a working hotwordenrollment apk attached if anyone is needing OkGoogle from anywhere working. OpenGapps has not yet fixed their packages, not sure if they're going to as they have been notified by a few people.
[Nexus 6P Original Android Development] nextrow01:
Could i just flash vendor, bootloader and radio.img in TWRP?
[Nexus 6P Original Android Development] Marcuss4:
Ah that is good to hear!

Thanks for your response [MENTION=5616748]ariefabuzaky[/MENTION]
[Nexus 6P Original Android Development] Jammol:
Looks red to me. Do you have a logcat by chance?
[Nexus 6P Original Android Development] NoobInToto:
12/12 build shows a changelog related to jio volte . Does this mean volte from jio works? Can anyone with jio sim (from India) confirm this?
[Nexus 6P Original Android Development] D@rekills4:
I will logcat it the next time it bugs out.
[Nexus 6P Original Android Development] razorloves:
https://review.cyanogenmod.org/176611
[Nexus 6P Original Android Development] sam3000:
[MENTION=614507]razorloves[/MENTION] has done further research on this and found a way to get over this particular problem. We'll loop back soon once we have good answers to questions like:

1) How do we get to a point where hotword works from clean install with opengapps.

2) How does a user recover an existing install to the point where hotword works.

In the meantime, I can confirm that we have perfectly functioning hotword once the setup problems are overcome (and the patch I previously mentioned is applied).
[Nexus 6P Original Android Development] wrkerr:
Any guesses on how to identify which "activity" would get me to the right menu to enable the WiFi Assistant? There are almost 200 activities under "settings" and 100 activities under "Google Play Services." I've tried all the obvious ones, and had no luck yet.

On a stock device, it would be an on/off switch for "Wi-Fi assistant" in Settings > Google > Networking.
[Nexus 6P Original Android Development] TheFrozen4:
I don't understand how the installer works.

I noticed that when I install a new system app (priv-app) that it gets deleted after every dirty flash. But, for example the GApps do not get deleted after a dirty flash.

How can I prevent my installed system apps from getting removed after a dirty flash, just like the Gapps package?
[Nexus 6P Original Android Development] boxguy1:
Move the PRIV apk in to system by using a root file manager
[Nexus 6P Original Android Development] TheFrozen4:
That does not prevent it from being uninstalled each time, the nightly dirty flash removes the copied file(s).
[Nexus 6P Original Android Development] boxguy1:
The Gapps is installed into Operating system when flashing but I think your PRIV app is systemless like Super Su and uninstalls every time you update
[Nexus 6P Original Android Development] amandeepparmar:
+1

Can anyone from India please test this ongoing issue?
[Nexus 6P Original Android Development] MechanicWB:
Will it work on a NBD90X?
[Nexus 6P Original Android Development] maximusmullivan:
Will what work?
[Nexus 6P Original Android Development] MechanicWB:
Will this rom work on a NBD90X?

Sorry if it is a stupid question, I'm a bit noob on this lol
[Nexus 6P Original Android Development] wilbarger:
If you are going to try to run the latest nightly, you will need to go to page one and download and install the latest Bootloader, Radio and Vendor Image.
[Nexus 6P Original Android Development] MechanicWB:
Ok, will do that, thanks ;)
[Nexus 6P Original Android Development] Donald Nice:
Guys, the cm installer checks the folder system/addon.d/ where backup scripts are placed before wiping system and installing the new nightly. The gapps use such a restore script. Check the folder and copy and edit or create a new script.sh for your app you want to be restored after a nightly flash.

Cheers
[Nexus 6P Original Android Development] TheFrozen4:
This .... this is the information I was looking for! I've found 2 scripts in there: 50-cm.sh and 70-gapps.sh (and some file named 'blacklist') that I can use to create an extra script. It all looks like some sort of advanced init.d implementation.
[Nexus 6P Original Android Development] Dark_Eyes_:
Any way I can help? It's been bugging me for a while lol. By the way nice find on the framework/av commit, awesome work there !
[Nexus 6P Original Android Development] razorloves:
[MENTION=1890382]sam3000[/MENTION]'s hotword fix is now merged. :good: So starting with the 15dec nightly, we can have it working. But you'll have to work around a couple issues.

1. The opengapps zip that people flash is replacing the good hotword apk that comes built into our rom, with one that's incompatible with the 6P. I spoke with the head opengapps guy (mfonville) a few days ago and we discussed a resolution to this problem. He will add a good compatible 6P hotword apk to the gapps zip. But until he does that, you have to replace it. Easiest way to do that is to edit the 70-gapps.sh script that's in this directory: /system/addon.d

Using a filemanager or anything else that works, open the file and remove any line that has HotwordEnrollment.apk. There will only be one or two. That will stop the script from replacing the one built into our rom. So after the next time you flash a nightly, you will have a good hotword apk.

2. The second issue is the incompatible hotword apk you had installed leaves incompatible voice model data on your device. So, you have to get rid of it. You can factory reset, but that's overkill. Just go to settings - apps and clear data on "Google App", and that will delete it. Another option to get rid of it is to go to the "ok google" voice settings in the google app. Click on "retrain voice model" at the bottom. If it is grey'd out, you have to toggle on "always on", then quickly press "retrain voice model" before it changes to grey'd out again.

Once that's done "ok google" will work from anywhere, even with screen off, if you have "always on" turned on.
[Nexus 6P Original Android Development] Jammol:
I knew I wasn't crazy when I thought they were using an incompatible apk!!!!ðŸ˜‚

Thank you for your diligence sir!!!
[Nexus 6P Original Android Development] Dark_Eyes_:
Oh my god it's so working! Thanks a lot [MENTION=1890382]sam3000[/MENTION] [MENTION=614507]razorloves[/MENTION], you did a very good job on this one.
[Nexus 6P Original Android Development] MidnightDevil:
Brilliant team work and collaboration from all parties! Well done guys, reall well done! :good:
[Nexus 6P Original Android Development] Hucci:
Hello, im on the latest nightly, what will happen if i lock the bootloader now?
[Nexus 6P Original Android Development] ariefabuzaky:
Why would you do that ?
[Nexus 6P Original Android Development] Dark_Eyes_:
Never relock the bootloader unless your phone has returned to a full stock Google image state. And doing so now would prevent you from installing new cm nightlies or other things.. Why do you want to do that?
[Nexus 6P Original Android Development] Hucci:
I just don't like the message i get when i turn on my phone...
[Nexus 6P Original Android Development] Therev86:
Then the best thing to do would be to fully return to stock, locking the bootloader on a custom ROM is a good way to end up bricked.
[Nexus 6P Original Android Development] FanDroid09:
LOL.
[Nexus 6P Original Android Development] jacndabx:
Wow, I've heard it all lol... Anyway I will give Cm 14.1 a spin this weekend when I'm off work and have time to set everything up
[Nexus 6P Original Android Development] blitzkriegger:
Hey Guys, I just wanted to report that F2FS (on /data) works on CM 14.1. I just had to decrypt by formatting data first, then changing /data to f2fs prior to transferring back my files and flashing. I also used the latest version of SuperSu and Flash Kernel.
[Nexus 6P Original Android Development] negrata:
Sure is responded, but I can't find it, so is there any way to hide the root icon on status bar without flash supersu?

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 6P Original Android Development] hectorviov:
Didn't find if there was any answers for this. I'm using WhatsApp with a custom ringtone. When I get a message it reverts back to the default ringtone, is this a known problem?
[Nexus 6P Original Android Development] fermentor:
Last night I tried to flash cm14.1 with f2fs on data. rom kind of booted but got a corrupt data message or something so had to flash the rom using ext4. can you please provide a step by step guide. which twrp did you use. ? How's your phone behaving with f2fs.
[Nexus 6P Original Android Development] Hateware:
Ehy, just asking, I've tried many custom ROM, I don't use CyanogenMod for a long time (latest install was around the end of november) so there's the question: this ROM come with blue accents and Pixel navbar animation or at least PIxel navigation button?
[Nexus 6P Original Android Development] aswinrj:
Whether this rom support for volte in Nexus 6p . I find the option to enable enhanced 4g but no response. Can you please reply . I want to use jio sim .
[Nexus 6P Original Android Development] ndarkside93:
You would need to use a kernel that supports f2fs. Jolla, And flash I know support it. I think racer does as well
[Nexus 6P Original Android Development] J0ESK0:
Followed these steps exactly but I still have the issue where the Always On toggle switches right back when enabling. I also noticed when installing the latest Open Gapps package it still installed "hotword" even though I removed the information from the scripts as you advised. Don't know what I did wrong. I am on the 12/15 nightly fyi.
[Nexus 6P Original Android Development] razorloves:
installing gapps again just undoes the fixing you did.

gapps only has to be installed one time per cm version. that's it. when cm15 comes, then you have to install new gapps.

now you have to redo the steps.

remove hotword lines from 70-gapps.sh, flash nightly, retrain voice model. that's it :good:
[Nexus 6P Original Android Development] J0ESK0:
Wow I didn't know that all this time I've been reflashing Gapps. Thank you sir, it's working perfectly now.
[Nexus 6P Original Android Development] negrata:
Same issue here, anyway I can't disable the live display.

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 6P Original Android Development] blitzkriegger:
I used the F2FS-compatible recovery provided by the Flash in his Ninja kernel thread. I also used his kernel as it's F2FS-compatible and plain awesome.

Below are the steps I followed:

Note 1: Doing this will wipe your data as well as remove encryption. If you prefer being encrypted, or if you have app data you intend to restore later then don't follow this guide.

Note 2: If you are flashing the latest nightlies do ensure you have the required vendor, radio and boot loader.

1.) First transferred all my needed data to my PC. Backing up is important as you will wipe all data later.

2.) Reboot to TWRP then go to "Wipe"->"Wipe data/factory reset".

3.) Next go to "Wipe"->"Format data" then type "Yes". Doing this decrypts your phone.

4.) On the main menu proceed to reboot back to recovery.

5.) Once back on TWRP I plugged my phone back to my PC then transferred back data and files to flash.

6.) Then I flashed in this order:"CM Nightly"->"SuperSu"->"Flash kernel"->then all my other mod zips.

7.) Lastly reboot system. Allow the system to boot and be patient. Mine took 3-5 minutes before it booted back up.

The phone has been running really well thus far. Apps seem to open a bit faster. That being said the speed difference is not like "night and day". Moreover the kernel and rom can be tweaked further to achieve or perceive the same results. Overall I think, at least for our phone, F2FS is a "nice to have" feature, but not a "need or must have"., especially considering you have to decrypt and format stuff.
[Nexus 6P Original Android Development] madsurgeon:
Have you granted storage permission for WhatsApp. The same happened to me, then when i changed the default ringtones, WhatsApp started to behave normally
[Nexus 6P Original Android Development] ~coolphoenix~:
Thanks, I had the problem with the clock app and custom alarms not sticking, now it works with storage permission!
[Nexus 6P Original Android Development] Imresaks:
What command should I use to flash radio and bootloader?
[Nexus 6P Original Android Development] xeonight:
I have yet to install cm14, but was thinking King about it here soon, how would I edit the gapps zip before installing the nightly so that I don't have to install, then edit addon.d, then reinstall nightly again and just for hotword?

I'm willing to do this but it just seems like it would be better to only do them once like normal

Edit: btw I'm currently on cm13 - 9/28
[Nexus 6P Original Android Development] razorloves:
You'll still have to edit the 70-gapps.sh first. But there's a gapps-remove.txt file in the gapps zip. Remove the line that has hotwordenrollment. Should work