yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] billku:
The 6p is the first android phone I've had without an sd card slot, so my question is, is there an emulated sd card portion of the internal memory that a data wipe doesn't touch? I ask becasue I'm used to keeping the settings I want to backup on the sd card, like Nova settings, Light Flow settings, so I can use them on my new setup. But I just realized if all internal data is wiped, that won't work. I know I can move the backups to my PC and then back again after flashing, but it would be easier if there was some kind of emulated sd card in the internal memory that a wipe doesn't touch. Any advice on this? Thanks so much in advance!

EDIT: I'm looking at root explorer and duh, emulated storage is there, where DCIM folder is, TWRP backup, etc. I'm assuming a data wipe doesn't touch the emulated folder, is that correct?
[Nexus 6P Android Development] terenchan:
Running fine here.
[Nexus 6P Android Development] micmars:
Yes, please.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

---------- Post added at 11:03 AM ---------- Previous post was at 10:53 AM ----------

No, there's not...seriously, why in the world would it even remotely seem like a good idea to ask for something from the dev that he would not even need to provide his users at this time?

You want a TWRP flashable vendor image...why? Because, it's not going to do you any good on this rom...as the base for this rom, at least for the moment, is from the December 2015 security release.

You want it? Grab the image files and fastboot flash it yourself.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] Krunk_Kracker:
Well...that's no good. Seems silly to remove the swipe up gesture.
[Nexus 6P Android Development] cd993:
I'll post them tomorrow. I've only just now installed BBS and it's only showing logs from now on, so tomorrow I'll not touch my phone in the morning once off charge until at least 3 hours have passed, or maybe even 4, and let's see if it drops from 100% in that time frame! I didn't receive any text/whatsapp/notifications in anyway today at that point so I wonder if that made an influence to not draining.

Though with 30 minutes light usage screen on time I'm now at 89%. Doing very well me thinks!
[Nexus 6P Android Development] inffy:
Umm no it isn't. Much more easier to long press. That is also one of the reasons why the navbar ring targets is not coming back anytime soon
[Nexus 6P Android Development] napes22:
Seems like an unnecessarily aggressive answer to his question.
[Nexus 6P Android Development] Fastrite:
You also have the option to just say "OK Google"

#whiteuimustdie
[Nexus 6P Android Development] sabbotage:
The December and January Vendor images are identical in size so I don't think they even changed. BL and radio are the same too. The only difference was the system image.
[Nexus 6P Android Development] gman88667733:
To flash the new update, will it wipe anything or can I dirty flash?
[Nexus 6P Android Development] nathanchance:
It is a complete rebase so I recommend doing a clean install. If you want to try a dirty flash, just make a backup first. If you run into any issues, just be sure to clean flash before reporting them.
[Nexus 6P Android Development] dirtyreturn:
I've read a post where a user successfully dirty flashed and didn't report any errors. Though, from reading it is suggested to clean flash.
[Nexus 6P Android Development] dex2grigg:
What files do you have to flash to get Franco to boot with this ROM?
[Nexus 6P Android Development] IberianPrince:
I dirty flashed with dalvik and cache wipe afterwards, no problems at all.
[Nexus 6P Android Development] eep2378:
No go!
[Nexus 6P Android Development] nathanchance:
UnSU, Franco Kernel, SuperSU 2.66. Flash them in that order and it should boot up just fine.
[Nexus 6P Android Development] DanRyb:
Also dirty flashed here and all seems to be fine.
[Nexus 6P Android Development] gman88667733:
Was it just the rom file that you flashed? If not, which files were needed?
[Nexus 6P Android Development] yvyv:
Where do I download UnSU.zip ?

Thank you.
[Nexus 6P Android Development] gman88667733:
Also... Why is UnSU and then SU 2.66 needed for this? Thanks!
[Nexus 6P Android Development] nathanchance:
Here
[Nexus 6P Android Development] Z-Man™:
OK guys I'm feeling a bit lost on this one. I want to use the crystaltronik dark layer. I've done a clean install with included root, I have busy box in xbin and layers manager from the play store. When I select the layers to install it shows them all installing but not all of the seem to be placed correctly. Some work but others don't change anything. When I open vendor/overlays with a file manager I can see that some of the apk are 0 bytes as if not being transfered correctly. Any thoughts or help would be fantastic. Sorry for the paragragh.
[Nexus 6P Android Development] yvyv:
Greatly appreciate you..
[Nexus 6P Android Development] gman88667733:
I can't find the UnSU file in this thread!! (Sorry to be a pain)
[Nexus 6P Android Development] micmars:
Perhaps, but do you think it's even the least bit reasonable to ask a dev for an ETA, much less to make your life more convenient for you by making a file that is already on Android File Host as a stand alone IMG file, and which you can already flash?

It's typically considered rude to ask for more free stuff. In what social situation do you think it's acceptable to ask a hard working dev to do more work for your benefit when it helps no one, not even the current rom users?

I help out when I can in these threads, and work pretty hard at measuring my words before I post, but when I see two people on the same page ask for the same thing--for the dev to take time out of his life for the user--I get a tad irate.

I hope this sufficiently contextualizes my response.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression

---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------

Me too...

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] CayenneGTS:
I have a Nexus 6 with Bean's ROM on it and I absolutely love it!!!! :good::good::good:

I'm going to install this version of the ROM on my son's stock Nexus 6P.

Is this all that's required:

1. Wipe data, system, cache, dalvik cache from TWRP

2. Flash PureNexus rom zip

3. Flash PureNexus Arm64 Gapps

I'm assuming more details such as the following is also implicit in the instructions above (this is what I followed for my Nexus 6:

Download ROM and GApps - copy to PC

Download TWRP 2.8.7.1

Backup any data I need to keep (in my case - music, sms log, call log, nova settings, podcasts, pics (I copied the pics from my Note 3 to the camera folder on my N6) - copy to PC

Unlock (toggle oem unlock in developers options), Root, flash TWRP using Nexus Root tool kit or Wugs tool kit.

Note: Unlocking wipes internal memory, so do this FIRST...then root, TWRP, etc

Note, you will have a stock phone and yet have the exact same file structure as it was before unlocking, etc...so, when moving items to your device from your computer, move the contents ONLY not the folders...so pictures go in the DCIM, camera folder...just the pics, not the folder. Repeat for all items. Under no circumstances would I copy folders from prior to OEM unlock, only their contents..you'll be glad for this.

Now, copy items from your computer, including the rom files, Gapps, kernel, etc. to the "SD" folder

Boot into recovery (TWRP) (power off entirely, then volume down, volume up and power simultaneously to boot into Fastboot mode, toggle to Recovery from there with volume buttons and hit power when you see "Recovery")

Backup stock setup

Wipe, advanced wipe, select everything but internal

Flash ROM, GApps

Reboot

Flash Elite Kernel

Reboot

After first boot, and you've set up Gmail etc, install Titanium Backup, etc and go about restoring that which is important to you (your Nova settings, mms call logs, etc).
[Nexus 6P Android Development] nathanchance:
It is at the bottom of that post, in the attached files section. You only need this if you want systemless root. Don't bother with it if you just care about being rooted as SuperSU 2.52 is built into the ROM.
[Nexus 6P Android Development] micmars:
Please let me see your free space available in the vendor partition...as below...that was a pretty massive theme...

My guess is that you may be out of space. Check if any of those layers apks are unnecessary, and if so, delete them.

I've found that once your free space in vendor drops below 5 MB, you're going to have issues.

This is a limitation of Layers, and one which I hope the Layers dev community is working to redress.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] IberianPrince:
Yep, just the ROM file
[Nexus 6P Android Development] micmars:
Can you tell me which themed app you flashed?

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] gman88667733:
Thank you, I appreciate the help
[Nexus 6P Android Development] Z-Man™:
[MENTION=5244502]micmars[/MENTION] which app are you using to view that? I'm an old ROM toolbox pro user and it doesn't give that info.
[Nexus 6P Android Development] micmars:
That's Root Explorer...though I think ES File Explorer can give you that as well.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] Constrabus:
-Flashed rom update, wiped cache / dalvik - android pay no worky

Since rom still comes with SuperSU 2.25, it overwrote my systemless I had set up on previous rom version

So I did the following:

Flashed UnSU and SuperSU 2.66 - android pay still no worky

[MENTION=3998937]surenther.ss[/MENTION] what did you have to do for android pay to work, do i have to temporarily disable root to add cards or something?
[Nexus 6P Android Development] surenther.ss:
[MENTION=1843981]Constrabus[/MENTION]

I followed [MENTION=6842057]nathanchance[/MENTION] guide

Wiped Everything other than internal memory

Flashed PN

Flashed Banks Gapps

Flashed FI Dialer

Flashed UNSU

Typed echo SYSTEMLESS=true>>/data/.supersu (In TWRP Terminal)

Typed echo BINDSYSTEMXBIN=false>>/data/.supersu (In TWRP Terminal)

Flashed Super Su 2.6.6
[Nexus 6P Android Development] chrisexv6:
Make sure you do both of the "echo " terminal commands from nathanchance's instructional post

I missed the first one because I didnt read carefully enough. Android Pay still wouldnt work so I went back and deleted the correct directory manually (/su/xbin_bind) and rebooted, then AP worked fine.
[Nexus 6P Android Development] Gytole:
Reflash vendor first. Layers ate sticking but cant install. A simple reflash of vendor in recovery cures my problems
[Nexus 6P Android Development] Constrabus:
Awesome, thank you both, that makes sense. Without those commands, its actually doing a system root.

However, I just did:

-Flashed UNSU

-Typed echo SYSTEMLESS=true>>/data/.supersu (In TWRP Terminal)

-Typed echo BINDSYSTEMXBIN=false>>/data/.supersu (In TWRP Terminal)

-Flashed Super Su 2.6.6

Now booting, I get "Unfortunately, SystemUI has stopped", gave it a minute, UI came back, but Android Pay still no worky.
[Nexus 6P Android Development] eep2378:
I've been using Coalesce layer. I flashed the theme ready beta zip( latest one), dialer and contacts , and hangouts. It booted but I got constant system UI and NFC, FC pop ups everywhere. Not sure if the new build is playing nice with the theme ready zip. I know there is an aroma install now but there are documented issues for some with that too. Honestly I'm not sure when the disconnect is.

Sent from the Nodes of Ranvier
[Nexus 6P Android Development] chrisexv6:
If you have a root explorer app can you check to make sure the /su/xbin_bind directory isnt there? I have a feeling it was there from your first 2.66 install and UnSU didnt delete it.
[Nexus 6P Android Development] Z-Man™:
[MENTION=5244502]micmars[/MENTION]

But that's without any layers installed I'll take another after I install them again.
[Nexus 6P Android Development] Z-Man™:
Will try thx. Do u flash vendor when flashing ROM or can I just head to recovery and flash it now while I've been running the ROM since last night?
[Nexus 6P Android Development] Constrabus:
Strange, I don't have directory named SU in /

I think you may be right, but I dont find anything doing a search for xbin_bind on /

Edit: perhaps I typed the commands in wrong via TWRP terminal, but essentially all thats doing is echoing attributes to the .supersu config. I'll attempt unsu and 2.66 install again.
[Nexus 6P Android Development] dragon1313:
dirty flash ftw!
[Nexus 6P Android Development] sneaky_zekey:
How do we disable force encryption. It did it automatically on first boot, clean install and how do we enable multi window view. Is there a thread for Q&A thread or is this thread used for that lol

---------- Post added at 08:43 PM ---------- Previous post was at 08:38 PM ----------

How are you guys adding color to the navbar and text, like google.
[Nexus 6P Android Development] MaliceOmega:
Ive done the echo cmds and reflashing super su 2.66 still telling me AP won't work on this version of android. Do we have to flash a different vendor IMG ?
[Nexus 6P Android Development] nathanchance:
Force encryption is disabled by default but that doesn't automatically decrypt. To decrypt, you need to format data in TWRP > Wipe > Format Data. This will wipe your internal storage and data partition to make backups. Multi window is in Settings > Developer Options. You can change the nav bar with a Layers theme. I believe that one is called Navigate and you can find it on the Play Store
[Nexus 6P Android Development] Constrabus:
Same here, starting to think its from dirty flash.

Did you dirty? If so, that might be why.
[Nexus 6P Android Development] MaliceOmega:
i was previously on Chroma and using systemless 2.61 and had AP working fine

---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------

well i did a full wipe coming from chroma. only thing i didnt wipe was internal and vendor

actually i used the pure gapps instead of the banks gapps. gonna see if thats the issue. Moral of the story: dont skip steps lol

EDIT: dirty flashed Banks gapps and AP is working fine. added cards and tested payment at my store and it worked without an issue
[Nexus 6P Android Development] Constrabus:
Interesting.

[MENTION=3186300]chrisexv6[/MENTION] and [MENTION=3998937]surenther.ss[/MENTION] have it working - what vendor img version are you guys on?

Edit: for the record, I'm on MMB29M
[Nexus 6P Android Development] bennyboy2120:
Is there any word on dirty flashing?
[Nexus 6P Android Development] nathanchance:
It was a complete rebase from the previous build so Beans recommended doing a clean install but there have been success stories of dirty flashing. Just make a backup and do a clean install before reporting issues.
[Nexus 6P Android Development] Mesmurized:
Hit & miss. Some have reported success, some have not.
[Nexus 6P Android Development] bennyboy2120:
Thanks I'll let you know
[Nexus 6P Android Development] MaliceOmega:
i dirty flashed banks gapps and AP is confirmed working here. thanks guys
[Nexus 6P Android Development] Constrabus:
interesting, I used Open gapps, funny how that matters so much

Edit: fitsnugly.com is down. anyone have official latest banks source?

Edit2: found - https://www.androidfilehost.com/?w=files&flid=41020 or http://download.dirtyunicorns.com/files/gapps/banks_gapps/
[Nexus 6P Android Development] MaliceOmega:
Must be something in them that modifies the system.img
[Nexus 6P Android Development] bsg411:
Just to confirm...this update is not based in the new MMB29P factory image right?
[Nexus 6P Android Development] eep2378:
Right.

Sent from the Nodes of Ranvier
[Nexus 6P Android Development] Bram77:
I just dirty flashed (system and cache wipe only) and all is working fine (with systemless supersu 2.66 and ex kernel 1.04). The only problem the previous version had and still exists (new device and clean install after inital unlock), is that swipe won't work on the aosp keyboard. With previous version SwiftKey worked fine but on the new version swiftkey is zoomed in very much (can see only a few keys). The same happens with the TouchPal keyboard.

I thought this might have something to do with the dpi settings (I'm @ 440dpi), but the option to change the dpi seems to have been removed from te settings.

Anyone else having the same problems?

Edit: google keyboard from the play store does function properly.
[Nexus 6P Android Development] HighDesertTrekker:
I can't get the WiFi to connect. Tried dirty flashing again but same result. Any ideas? Goes to connect but hangs on getting IP.
[Nexus 6P Android Development] Krunk_Kracker:
Long press brings up Google On-Tap, which is useful. For work I get tons of addresses and phone numbers texted to me and it works great, but I also like using Google Now, but there's not a native shortcut to get to Google Now.
[Nexus 6P Android Development] Kris Nelson:
But there is.. Lol.. Click the G when you bring up on tap
[Nexus 6P Android Development] welcomebob:
Noob question

So in more technical terms what does a complete rebase mean anyhow? I'm technical but somewhat a linux/android noob. Will it be like CM and he will now have to manually put in each and every update into his ROM or still just the simple grab and compile. Again noob question, and might be worded horably so hopefully you understand what I'm trying to get across, but would love to learn and understand the rebase thing :D Thanks in advance.
[Nexus 6P Android Development] nathanchance:
Check out this post. You can still edit the DPI until Settings > Pure Nexus Settings > Tools and info > Build prop editor and looking for ro.sf.lcd_density.

I am probably going to botch the explanation myself but no, he can still merge the changes from AOSP. It just means that he redid the base of the ROM (resyncing source, cleaning up code, etc) in a major way.
[Nexus 6P Android Development] chrisexv6:
Pure Nex 1/3 was the first 6.0.1 ROM Ive flashed on my phone, so coming from Chroma 6.0 build I grabbed the "NOT FLASHABLE" zip (https://www.androidfilehost.com/?fid=24269982087013347) and used fastboot to flash the December (MMB29M) vendor and bootloaders (I did *not* flash the new modem because of the LTE issues it may be causing)

Booted back into recovery, did a clean wipe and then installed PN, Banks dynamic Gapps, ran the terminal command, installed the UnSU zip, installed AK Kernel v .20, then installed SuperSU 2.66 systemless.

Upon first boot AP wouldnt work because I had missed the reference to the first terminal command in the "for 2.64 and above" instructions, so I manually deleted the /su/xbin_bind directory, rebooted and then AP started working.

From my experience on Chroma, the only thing Ive done that caused AP to break was using incorrect Gapps. Any Gapps other than Banks Dynamic would break it. It sounds like beans now actually knows how to get AP working in the ROM *and* Gapps so there should be more Gapps (and maybe even more ROMs!) that become options if you want AP.
[Nexus 6P Android Development] micmars:
Definitely it's the size of the individual layers in that theme...just as an example, the Chrome layer is 1 megabyte.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] baronmax:
Hey guys, does this work flawlessly with ProjectFI? I've installed ROMs on other devices, but I am a bit leery about installing a new ROM since I'm using Fi. What exactly is that "Google Fi Dialer" that is in the OP? Does anyone know what that does? Anyone else here using Fi with this ROM?

Thanks. :)
[Nexus 6P Android Development] giant22000:
Anybody having issues with WiFi calling on latest build? My phone refuses to connect to WiFi calling on latest build. WFC is turned on in settings with WiFi preferred selected.
[Nexus 6P Android Development] micmars:
None whatsoever...though I'm on the older TMO band 12 modem.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] giant22000:
I used banks gapps and cleaned flashed. Think that could make a difference since I didn't use the recommended gapps?

Kinda weird because I've never had any issues with wfc.
[Nexus 6P Android Development] nathanchance:
The Google Fi Dialer is needed for full Fi support (primarily Wi-Fi calling). It is just the Google Dialer that is included with stock Android. You just need to flash it in TWRP.
[Nexus 6P Android Development] micmars:
The fi fix includes the following items, helpful for non-fi users who want to have the enhanced features of the Google Dialer (block contacts and lookup feature...though lookup is also in the AOSP dialer)...

1. Theme ready Google Dialer

2. Telecom and teleservice apks

3. Google Dialer java archive file

Aside from the above features, it is needed if you're using Project fi (that jar file is pretty important).

Also, please note that if you're using Project fi, your modem must match your vendor image build date, so you won't have the luxury of swapping out different modems.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Android Development] fadac:
I'm using Fi flawlessly. Haven't had any issues with this ROM and have been using it since it was released. I travel across 3 states in the midwest for work and connect fine all over. WiFi Calling also works.

Edit: FYI, I'm currently on 1/3 build with MMB29M vendor/modem/bootloader, PN GApps, & SU 2.52. I have used Xposed & Busybox without issue. Newer versions of SU have given me boot problems.

Not sure if your last comment is correct, I remember at the beginning I was trying different modems with the same vendor image and had no issue. Not sure if that has changed with the latest modems?
[Nexus 6P Android Development] baronmax:
How did you do the install, Fadac? Just the same as it says on the first page with the Google Fi Dialer? I've had 2 android tablets and 3 android phones, all customized with ROMs and kernels, but for some reason, this one has me on edge. I get this feeling that ProjectFI isn't the same as the regular cellular service in terms of how it works and I really don't want to mess it up because the service is working so amazingly. There are, however, a lot of customizations in this ROM that would really make my phone better.

Also, does this ROM have OTA updates? Or do I need to install the later releases in order to upgrade?

Thanks. :)
[Nexus 6P Android Development] nathanchance:
Can't answer the first part as I am not on Fi but there is not an OTA process built into the ROM. You can follow the Pushbullet channel here to get alerted of new updates and most updates you can just dirty flash so you don't need to setup again.
[Nexus 6P Android Development] fadac:
Yes, just as OP states and flash Google Fi Dialer at the end. As i've said, I haven't had any signal issues in the midwest. Take the leap, if it breaks it you can always go back to stock! This ROM is worth it.

I don't use OTA.
[Nexus 6P Android Development] Krunk_Kracker:
Eh... It's more steps. I guess I just don't understand why they removed the swipe up shortcut.
[Nexus 6P Android Development] tseven:
Any ideas how to fix 1password keyboard issue?

1password Uses a custom keyboard for filling in login info.

Click on a text field, switch to the 1password keyboard and after filling in the info it will switch you back to your default keyboard. This works fine on stock.

There is a bug with certain ROMs (PureNexus & Chroma so far) which breaks the 1password keyboard. The keyboard fails to fill in the info and will disappear.

Others have experienced the same issue:

https://discussions.agilebits.com/discussion/49766/autofill-not-working-on-custom-rom-chroma

http://xdaforums.com/nexus-6/help/qa-chroma-01-11-2015-t3000186/post60273070#post60273070

http://xdaforums.com/nexus-6/help/qa-chroma-01-11-2015-t3000186/post63480288#post63480288

Any suggestions/help in resolving this is greatly appreciated.

I'm willing to contribute to a bounty.

Thanks!
[Nexus 6P Android Development] Persianhawkes:
Someone should start an Android Pay on PureNexus discussion thread.