yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] sengab1991:
Substratum isn't working on the last build :/
[Nexus 6P Android Development] kyzn:
Works fine. Maybe it's the theme you are using.
[Nexus 6P Android Development] sengab1991:
I installed the application substratum and then installed Domination theme and applied it.
[Nexus 6P Android Development] kyzn:
Did you try another theme? Domination is a favorite, I don't personally use it but people haven't said they encountered any issues.

I use Mono/Art and Spectrum. Both applies without any issues.
[Nexus 6P Android Development] grimloktt:
I removed one of the tiles and still can't move an application tile up. It must be a bug...
[Nexus 6P Android Development] hinxnz:
You can but you need to drag all the tiles in the second to last row into your quick settings area, then you'll be able to add the ones from the last row. Once you have added the one you wanted, remove the ones you had to add to get the one you wanted there.

If you added all the tiles from the second to last row and you still can't add one from the last row, then you may have an extra row than me, so you would also have to add the third to last row too before adding the one you want from the last row.
[Nexus 6P Android Development] j.a:
The newest rom is running great except that when trying to use the phone via the "phone" icon the phone apk crashes. I can make calls going through other apps like Textra or Contacts but I cannot get to the dialer. Anyone else experience this or know a way to fix it?
[Nexus 6P Android Development] elchingon:
Go in settings>apps> click on the cog icon on the top right>Phone app> choose your phone app.
[Nexus 6P Android Development] Izeltokatl:
Without doing build prop edits, you'll need to down grade the wear app on your phone. In using the Huawei Watch with the same issue. You should take this question to the Huawei threads.
[Nexus 6P Android Development] j.a:
Thanks for the quick response,

I checked the setting above and the "Phone" was listed as the system default and the only option.

I still get the following error:
[Nexus 6P Android Development] bigknowz:
Shanghai Adups

Any cause for concern here? Secret Backdoor in Some U.S. Phones Sent Data to China, Analysts Say
[Nexus 6P Android Development] Gizmoe:
I would say no. Nexus and Pixel devices are completely controlled by Google on a software level. This seems to be affecting those "Budget" models that come with a lot of manufacturer installed software. ZTE and Huawei make a ton of those models. The 6P was a contract from Google so they did not have control over the software. And Google would have caught something like that anyways if they even tried to install something.
[Nexus 6P Android Development] fearsparks:
Anyone else still having issues after changing the ro.build.type to user from userdebug? I still get the same message.

And by Wear 2.0 Beta do you mean joining the developer preview and installing the associated testing version of the Android wear app? I just joined the channel, but I don't think the update to the app has pushed yet. It says it can take several hours.
[Nexus 6P Android Development] Donjuanal:
Did you reboot after modifying build.prop?
[Nexus 6P Android Development] fearsparks:
Sorry, forgot to include that. Yes, I rebooted a couple times hoping it would also trigger the developer test build of android wear update.
[Nexus 6P Android Development] Franzie3:
just google the APK and download it. probably easier that way anyway
[Nexus 6P Android Development] fearsparks:
So I uninstalled android wear then goggled and downloaded android Wear 2.0.0.134587396 beta and I'm still getting the same error.

I ran PN marshmallow before and everything was working. Even so, I did a clean flash to upgrade to N yesterday which is when this stated. Ran stock kernel for a couple hours before moving to flash kernel. Don't think I checked android wear before changing that, but doubt it's kernel related right?
[Nexus 6P Android Development] c_86:
Not sure why you are having these issues. All looks correct. I had the same problem until I did the build.prop changes and then it was fine. Try wiping the cache in the app and reboot again. See if that helps
[Nexus 6P Android Development] Donjuanal:
And your build.prop edits are surviving reboot as well?
[Nexus 6P Android Development] fearsparks:
Thanks to both of you for your help. I did one better C_86... I did another clean install. Wiped cache davlik system and data in twrp 3.0.2. Installed 10-25 PN again, dynamic apps, flash kernel, then super SU zips in that order.

Booted into android and literally just signed in, went to the play store and installed root explorer. Changed my ro.build.type to user. Rebooted and verified the build.prop changes persisted. Installed android wear opened it up and I'm still getting the error.

No clue where to go from there. My android wear app details are attached. Is this the same version the play store serves you guys?
[Nexus 6P Android Development] jmaclean62:
I am looking to roll my phone back to the August build of Marshmallow. I want to mirror my phone on my Pumpkin Head Unit in my truck and it won't mirror with 7.0. I am presently on PN 7 10/25 build/twrp -3.0.2.-3- Can I go back with problems with a clean flash and if so, where can I find the files stored. I have spent 10 minutes looking. Maybe they are under my keys and wallet? :)
[Nexus 6P Android Development] rchtk:
Google doesn't necessarily have the source code of the radio hardware vendor driver. Android interfaces to it with an abstraction layer through in/out callbacks.

Now if we are talking about application interaction that would require a second communication channel. Such a covert channel was discovered on Samsung devices a few years ago.

Depending on who discovers it and who is actually snooping on the data, a backdoor will be called a feature........
[Nexus 6P Android Development] Gizmoe:
Yes you can go back by clean flashing just fine.

https://www.androidfilehost.com/?w=files&flid=43154

---------- Post added at 01:31 AM ---------- Previous post was at 01:19 AM ----------

It was actually written as a "feature" for chinese manufacturers. It was not supposed to be installed on American versions. You are correct that the radio firmware is not written by Google, I won't argue that. Google would have picked up on it though in their testing of the device. It's not hard to find if you are experienced at looking for that kind of thing. It's not something that the engineers at Google could have overlooked IMO. But without an exact statement from Google, I suppose we can only speculate. I doubt it's an issue though.
[Nexus 6P Android Development] biff6789:
We’re not fully in the clear just yet. Adups hasn’t yet published the list of specific Huawei models affected, and everyone saying “it’s only low budget phones that were targeted” is ultimately only guessing and making that assumption based on an incomplete set of data.

While Google maintains Android and the Kernel, that is only part of the software experience on your 6P. Google doesn’t fully control all firmware/hardware drivers, and they certainly don’t control the closed-source RIL (which is where the NSA snuck in their dirty spy code) – none of that is published in Google’s AOSP, and I don’t recall ever seeing evidence that Google formally signs off on and verifies ALL hardware and radio interface layer code. While they may have been heavily involved in the 6P’s design and production, anybody who has ever worked with Chinese manufacturers knows that you need to be vigilant in ensuring you have checks at EVERY level in production, otherwise it’s very easy to sneak this kind of nonsense in.

Also, don’t forget this has happened before. We’ve already been through this twice now with CarrierIQ and then again with what was revealed in Snowden’s leaked NSA documents – and in both of those cases virtually all users got burned. Stating that we aren’t compromised by this particular spyware is a bit premature at this stage. In the interest of keeping this discussion relevant to this ROM, it doesn’t appear that it’s something hiding in Android that could be patched out by the Pure Nexus team either. The report said that this is firmware-level snooping.
[Nexus 6P Android Development] jmaclean62:
What about the correct vendor image and correct GAPPS? I don't see them there.
[Nexus 6P Android Development] Gizmoe:
You will have to dig around on beans file host. I know everything is there.
[Nexus 6P Android Development] RayMcGrath:
Perhaps wait for the new build. See if a clean flash will fix it. I've got a feeling it's coming soon.
[Nexus 6P Android Development] c_86:
That's odd man.... I have the same version and running essentially the same as you. I don't know what to recommend. I'm at a loss at this point. You aren't missing any thing...
[Nexus 6P Android Development] Franzie3:
Change that other user debug to just user. I have that on mine. I might have done both and just never realized. I know mine works flawlessly
[Nexus 6P Android Development] antiochasylum:
OMS support coming very soon... No fonts. Just themes.
[Nexus 6P Android Development] grodri19721:
Pure nexus app

I flashed rom but dont have the pue nexus app to customize rom
[Nexus 6P Android Development] chikimonke:
They've gotten rid of the app, at least for now. All the customizations can be found in the system settings.
[Nexus 6P Android Development] grodri19721:
Ah ok thank you
[Nexus 6P Android Development] Samuel Holland:
Pure nexus #1

Hi Sir Nathan, I just wanted to say thank you sincerely for all that you contribute and by helping Angler to be #1 in my opinion right now still running 6.0.1 since I believe your ROM is close to perfection. I'm gonna have to double down developing wise to try and catch up to functional in order to update myself when needed. Also thanks for the post in building nougat pure nexus. Anyway I just wanted to say I've used a few and have to say in my opinion nothing comes close to your ROM. Thank you and may the good Lord bless you and family. ?
[Nexus 6P Android Development] BeansTown106:
thats a bug with the facebook app even happens on my parents old galaxy s5

honestly purenexus has no built in ad blocking lol.

yep :/ this is why google removed it on 7.1 and redid it for the pixel devices

the upcoming release is done, just building as we speak, i will add them in the next build though, if i kept going this release would take even longer haha

im not sure if it will, i would need to test and i currently dont have a daydream, sadly i ordered my pixel on the 21st so i dont think they are gonna give me a free one either :(

yes it will be exactly like it was in 6.0.1

bug in the package installer, blame google, however i have fixed it and it will be in upcoming build

just a easter egg, part of the substratum app

three seperate vendors, custom vendor tell the system which packages to build, selinux modifications, overlays, etc.

proprietary vendor is the system related proprietary files from google

vendor image is the vendor image supplied on newer devices. ideally all proprietary vendor files should be in the vendor image and not in the system but google be lazy :P

tldr you need to flash vendor images, and custom vendor has nothing to do with proprietary files and doesnt get overwritten by vendor image

real mature, why are u in my thread again? lurking to see if there is anything new to kang?

can u try without the audio mods :P and then report if it still happens i have not had this issue

is this all of the combinations, other than per app? gives me an idea to expand the expanded desktop tile to be more advanced :good: :D

na i dont see any issues with the 6p, [MENTION=2376614]jcase[/MENTION] was actually the one who originally found these backdoor a few years ago. reported them to the appropriate people, and basically got ignored, now this new research firm comes around and grabs the fame :confused: point being i doubt google would ignore this if it was present on their devices, this is mainly low end phones

Oh ya.. update script is running :cool:
[Nexus 6P Android Development] mikeandjaimie:
Holy **** dude.. Breathe! That was one hell of a post lol And thanks for such great releases, keep them up and can't wait to see what's next!
[Nexus 6P Android Development] buzzwyzr:
Haha! Owned!!
[Nexus 6P Android Development] BostonDan:
I think you mean Pwned. :)

Cheers,

B.D.
[Nexus 6P Android Development] Lawlrus:
[MENTION=4395895]BeansTown106[/MENTION]

Aye, he made a post about trying to ressurect chroma, expect an epic ton of kangs coming shortly lol.

After his temper tantrum in his shamu thread I was hoping he'd at least disappear until he was old enough to buy a pack of smokes. No such luck
[Nexus 6P Android Development] RED ZMAN:
Checked out the changelog, very nicely done. A shame we'll still be on Legacy Substratum from what I see, but the phone reboots pretty darned quick these days. I was wondering if you could get this in on the next release if you have time?

Thanks as usual, I've been sitting on the last MM Build because it is so stable and had hold back to kill. I finally get to get on Nugat.
[Nexus 6P Android Development] BennyTwoThumbs:
So i recently got my friends old Nexus 6P, he upgraded to the Pixel, and coming from the LG G3 rooting and flashing roms, I got the Nexus unlocked and rooted and started to hunt down roms... Would love to give this rom a shot but im at a wall... The phone i have is updated to 7.1.1 and Build Number is NPF10C. I am going to use project FI, so i got the Pure Nexus rom, the Dynamic Gapps, the Google dialer, and I am stuck on what Vendor image I need, or if one is even needed. Any help is much appreciated. Thanks.

Edit: attempted to search / hunt through the pages for an answer, no luck =/
[Nexus 6P Android Development] weedeater84:
Vendor Images(flashable by twrp image option): https://www.androidfilehost.com/?fid=312968873555003531
[Nexus 6P Android Development] Lawlrus:
Takes you right to the information when you click on the link to DL the ROM
[Nexus 6P Android Development] weedeater84:
sweet status bar !
[Nexus 6P Android Development] BennyTwoThumbs:
Right, but it brought me to a list that none of them match my build number so i was unsure what one to use.
[Nexus 6P Android Development] weedeater84:
i shared with u the direct link
[Nexus 6P Android Development] BennyTwoThumbs:
Thanks!
[Nexus 6P Android Development] Lawlrus:
No. When you click on DLS in the op, and it takes you to the post he made I took a screen shot of, and you click on the vendor file, it takes you directly to 90x. I just did it
[Nexus 6P Android Development] Lord. Tech:
[MENTION=4395895]BeansTown106[/MENTION] so i take it DUI Flingbar didn't cut it for this update lol. But plz consider it for next update, it would make PN perfect for me
[Nexus 6P Android Development] Fatchoco06:
So I upgraded my ROM to Nougat, and now wanted to downgrade it back to Marshmallow. Do I just install the older version of the ROM? Do I have to install a different version of GApps and Vendor Image as well? Thank you very much!
[Nexus 6P Android Development] RayMcGrath:
I wouldn't count on DUI in PN. (just my hunch)
[Nexus 6P Android Development] XzavierL:
I am having this issue as well with my bottom speaker. Noticed it when playing a game the bottom speaker would fade in and out or sometimes stop playing audio all together. Not sure what the cause of it is prior to reading your post I just figured my speaker was busted.
[Nexus 6P Android Development] FanDroid09:
Yes.

You should flash the proper MM vendor image, clean flash the MM rom, and flash MM gapps.
[Nexus 6P Android Development] RayMcGrath:
Yes. Start over clean with rom, correct vendor image. A safe way would be to go back to stock marshmallow tar.
[Nexus 6P Android Development] Lord. Tech:
I wouldn't have either, but Beans was kind enough to agree to checking if DUI is compatible with aosp and since i know a few guys on his g+ have already made personal roms with DUI, so probably when he gets some free time to test it im sure he'll give it a fair shot.

So i have my fingers crossed for now :D haha
[Nexus 6P Android Development] BennyTwoThumbs:
OKay, so now im having an issue, when i try to make a call or receive a call, my phone softboots. I tried both the Oct and Nov version of D Gapps. also set the default app to Phone. No luck still softbooting.

Again, Using project fi, also flashed the Fifix. hmm

Found this

November 14, 2016 | 9:23am by sjgoel in Nexus 6P Android Development

I had similar problem after flashing the FiFix Dialer. The phone would soft boot when I tried to call or received a call. Dialer defaults were correctly selected. Nothing helped & I had to clean flash the ROM minus the FiFix. That settled the soft reebot. I am on T-Mobile and wifi calling works fine. →

Guess I can try with out the FiFix, but isnt that needed to work with project fi?
[Nexus 6P Android Development] budeone:
I was just reading the "Upcoming Release Rom changes" . That is when I am going to download and install on my friend's phone. That looks like the ticket!!
[Nexus 6P Android Development] ohlin5:
I don't use Fi, but I believe it's been said before that the FiFix is no longer needed. Someone can correct me if I'm wrong but I believe I've seen this posted before.
[Nexus 6P Android Development] pamplona!:
My ok google voice detection was working fine on marshmallow but i've upgraded to nougat using the tutorial in here, down to the letter, but its still not working.

In fact I did it twice but still no dice. Any ideas?

Just to clarify: google now works when i press the microphone button and speak into the phone but it wont detect my voice from a locked screen, or home screen, or any on screen. i've deleted the voice and retrained, turned off/on wifi, all to no avail.

thanks.
[Nexus 6P Android Development] ohlin5:
What GAPP's are you using? Probably not the latest ones linked in the OP I'm guessing, as this is a symptom of that.
[Nexus 6P Android Development] pamplona!:
i am using PureNexus_Dynamic_GApps-7.x.x-20161009.zip

474.9MB Oct 09, 2016 | 09:51PM

which i downloaded from here: https://androidfilehost.com/?w=files&flid=47350

assumed to use the one with the most recent date. is this correct?

thanks.
[Nexus 6P Android Development] ohlin5:
Yeah, those are the latest ones. Did you totally clean flash the 10/25 ROM along with those or did you do something else?
[Nexus 6P Android Development] TheCuteCriminal:
Not getting messaging texts like WhatsApp verification code and Google 2 step verification code... But able to receive from other local service providers.. I am on 6.0.1 latest build.. is this an issue or its just me getting it?
[Nexus 6P Android Development] JaZart:
Anyone else having memory issues. Only 25 hours of uptime and system is using 1.5-2.0gb of ram.
[Nexus 6P Android Development] dunny_:
Very poor battery on this latest build. Draining very fast even when screen is off.
[Nexus 6P Android Development] nathanchance:
So run BetterBatteryStats to find out what is keeping your phone awake. I am getting great battery life on this ROM. Battery life is rarely a statistic that falls under the ROM. It is usually a user space statistic, means you have nearly complete control over it. Find out what is draining your phone and nuke it.
[Nexus 6P Android Development] cbrehob:
Do not use battery savings mode with this ROM. I have had constant problems since.
[Nexus 6P Android Development] asif9t9:
Lol if only all answers were that simple. Thanks. Will reload later.

Btw is it true from some reading that this might be the last time we need to update that file? Like, for future marshmallow updates?
[Nexus 6P Android Development] dunny_:
Nothing has changed in my usage other than the rom
[Nexus 6P Android Development] jesssiii:
Systemless only refers to where su is, it doesn't prevent system alterations. And Chainfire indicated it was going to most likely be the standard going forward. What is the problem, could you refer me to the info I can read? Since you cannot hear my tone, let me add that I say this respectfully, just seeking my own clarification. ?

I'm working this weekend, so haven't gotten a chance to flash this rom yet, but really looking forward to it!
[Nexus 6P Android Development] micmars:
Uhm, I meant it in a broad sense, not in a strict sense.

Broadly, systemless root is in its nascent stage, and perforce will have bugs (Chainfire writes precisely that in his posts on the method). Further, the dev of this rom has made a few things abundantly clear...he will continue to package the rom pre-rooted, so that if you encounter issues and choose systemless root, he won't try to isolate the cause for you...and secondly, you are encouraged to try your own setup (Xposed modules, pick your own kernel, etc), with the community here to help.

Specifically, most report all apps working sans issue with systemless root, and practically speaking, you should be fine...just don't be shocked if a few root apps don't function.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] kbapk:
Anyone know is possible to download Latvian language for AOSP keyboard?
[Nexus 6P Android Development] Quie2TP:
I don't believe so. I have had to do a reset of my watch when I do a clean flash.
[Nexus 6P Android Development] NovaSlim:
There is no such thing.
[Nexus 6P Android Development] KennyG123:
That doesn't mean that an app hasn't updated and gone crazy draining your battery. My battery life has not changed updating this ROM.
[Nexus 6P Android Development] :
This should be great..
[Nexus 6P Android Development] adamo86:
Can this rom be flashed if the device is rooted via systemless root
[Nexus 6P Android Development] micmars:
Exactly.

Apps that haven't been updated to accommodate Marshmallow seem to be from where the biggest battery drains are coming.

Zooper in particular is draining the heck out of my battery, which is just such a bummer, because I really love its customization options.

I've been looking at KLWP, and though intimidating, it does seem to be the wave of the future. I am going to bite the bullet and learn the bloody thing.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] dunny_:
I absolutely agree with you however, I don't allow my apps to auto update and nothing else has changed other than this new build, my previous builds had incredible battery
[Nexus 6P Android Development] KennyG123:
Have you checked for Google Play Services drain? I get that every time I have pending updates. As no one else is complaining about worse battery life something is going on in your setup. You need to take steps to find it rather than blame the ROM. We are only trying to help you.
[Nexus 6P Android Development] micmars:
Here...you may want to do this...

1. Install Better Battery Stats or similar app, reboot, fully charge, turn off WiFi

2. Put your phone down and let it rest for about 20 minutes

3. Use it for about 10 minutes, real world use, text, post, scroll through a bunch of stuff on your browser, etc (ie, don't just sit and watch a YouTube video)

4. Put your phone down again, 20-30 minutes

5. Another 10 minutes of fairly heavy use

6. Repeat for another 2 cycles (use for 10, idle for 20-30)

Report back with screen shots of the default screen on Better Battery Stats, and then the partial wakelocks screen.

We should be able to block and tackle this pretty quickly.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] kbapk:
Can I use elemental kernel for this ROM?