- The dev was kind and generous enough to build the N6 ROM after asking. As of now I have only found 2 minor bugs that are easily resolved. It is definitely a daily driver with WiFi calling, VoLTE, and camera all working.
If any of you are interested in this please pm or respond. If there is enough interest I'll update this post with links for download.
***Edit*** Here are the links if you are interest. This ROM is based on Lineage OS & updates OTA (the update is pushed by the developer and is downloaded/installed like stock). Please reach out to the developer to show your appreciation. Maybe he will "officially" begin to develop for the N6.
Look here for further information about the ROM:
Here's his N5 page on XDA.
Here's his N6P page on XDA.
Installed Prerequisites: Update to the latest TWRP, Radio, & Bootloader
- 3.1.0-0 TWRP --> or use the "Official TWRP App" from the Play Store.
- Newest Bootloader-72.01 --> Source
- Newest Radio-05.44 --> Same source link as the Bootloader.
ROM & Gapps
- DARK ROM: Nexus 6
- Dynamic Gapps --> Source
Backup first... always backup first
Wipe system, data, cache and dalvik cache
Install DARK ROM
Install provided GAPPS (Mandatory)
(Optional) Install root package of your choice (I recommend Magisk)
Potential bug: Unable to send MMS Message while connected to WiFi:
- For T-Mobile at least (might be the same for other carriers) under "T-Mobile MMS" APN you have to change the "APN protocol" to IPv4 (default is IPv4/IPv6 but it also doesn't work on IPv6 either) or your MMS will not send.
- Change the APN Type in the "T-Mobile US LTE" APN from "default,supl" to "default,supl,mms"
Please report back if you find any bugs!03-20-2017 08:50 AM
- 03-20-2017 10:30 AM
Also, a perk for this ROM is that it can update like stock (Delta Updates). The dev can push a new build out once it is completed which is a very neat feature!03-20-2017 10:52 AM
- 03-20-2017 04:46 PM
- I left the bootloader unlocked because I wasn't expecting to get any further OTAs from Google anyway. I've never flashed a recovery or a ROM, but I use the full Android SDK for sideloading. I've read through some stuff about flashing ROMs; I've just never had a compelling reason to go for it.
I'm assuming you have sideloaded at least February's 7.1.1 so you should have the latest bootloader and radio...
If you want to proceed:
Download TWRP recovery here (click on "Download twrp-3.1.0-0-shamu.img") and place it in your "platform-tools" folder just like you would with your sideloadable files.
1) Perform the steps as if you were to unlock your bootloader or sideload again so that the phone is at the bootloader screen and you can type the commands on your computer.
a) Go into Developer Options and enable USB debugging.
b) Plug your phone into the computer.
c) From your computer, open a command prompt and typeCode:
adb reboot bootloader
2) Now flash TWRP by the commandCode:
fastboot flash recovery twrp-3.1.0-0-shamu.img
3) Now check to see if the new TWRP is there.
- Reboot the bootloader byCode:
- You can go ahead and reboot the system now.
Post back when you've completed this.03-20-2017 10:48 PM
I'll PM you the links for download and other information.
Here are the flashing steps:
1) Download the ROM and Gapps onto your internal storage.
2) Back up any important data.
3) Now boot into recovery (TWRP).
4) Make a Backup (Optional but highly recommended). Just in case something happens it is always good to have 1 good backup.
- Backup>Swipe to Backup
- The default selections (System, Data, & Boot) are all that you need.
5) Wipe Data
- Wipe>Advance Wipe>Select Dalvik/ART Cache, System, Data, & Cache>Swipe to Wipe
- DO NOT WIPE INTERNAL STORAGE!
- I usually perform this step more than once since I've had issues going from one ROM to another. It seems like doing this wipe multiple times in a row clears it up.
6) Install ROM
- Install>Select ROM ZIP file>Swipe to confirm Flash
7) Install Gapps
- Install>Select Gapps ZIP file>Swipe to confirm Flash
8) Reboot System03-21-2017 01:03 AM
- After getting past an odd experience flashing TWRP, the ROM seems to be working fine on my N6 on Project Fi. TWRP kept disappearing after a reboot time after time until it finally didn't: it only stuck after I flashed TWRP (for the fourth or fifth time) and then immediately flashed the ROM.img and Gapps. (Thanks to ProBird79 for convincing me it would work.)
WiFi calling is working, and I can send and receive MMS messages over WiFi as well: I think Fi's APN Protocol is IPv4. Bluetooth pairing in my Sorento was successful, but a little painful since it took the phone several minutes to identify the car by name instead of its bluetooth address. (Pairing is confusing when all you see are 5 or 6 different BT addresses and one of 'em is labelled with a headphones icon--and who knew that one would be the car?) Voice training also took longer than I'm used to. I've always made it through that process on a first attempt. This time it took nearly 10 tries before I got a thumbs up from the phone. Of course, people have widely different experiences with voice recognition anyway, so there's no obvious conclusion to draw.
It hasn't been a full 24 hours yet, but the phone seems to be sipping even less power when idle than it did running stock, but time will tell on that score. Beyond that, there's nothing to report except that I now know with certainty that I do not like the look of the Pixel launcher. A mocked-up version in Nova looks a lot more elegant to me.
One oddity: my phone is now always connecting to T-Mobile LTE when it's not in airplane mode; before, on stock, it connected to Sprint around 80% of the time. And, no, I didn't flash a new radio: the phone's been running the 5.44 radio for the past two weeks.03-22-2017 12:06 PMLike 1
Also, from what I've read Project Fi "learns" connectivity and stores it locally so maybe performing a clean install erased that data and is now relearning? Maybe T-Mobile upgraded their towers and you now have a stronger signal with them?
Supposedly Lineage OS works with Project Fi and since this ROM is based on it I wouldn't think there would be any problems. Who knows, maybe in this build it is broken...
A few possible solutions I've read using Project Fi with Lineage OS and switching issues:
1) Have you enabled all permissions in the Project Fi app (I read where this resolved one person's issue)? Settings > Apps > Project Fi > Permissions > Enable all of them.
2) Uninstall the updates for the Project Fi app > Reactivate the phone with Project Fi > Restart the phone > Install the updates for Project Fi app. (Source) I wouldn't think this would do much since you did a clean install but it's worth a shot.
You can try force switching for testing purposes. Which connection is stronger?
Force Jump to Sprint: **#*#34777#*#*
Force Jump to T-Mobile: **#*#34866#*#*
Force Jump to Next Carrier: **#*#346398#*#*
Turn On Auto Switch: **#*#342886#*#*
Repair Bad Activation: **#*#34963#*#*
Current Network Info: **#*#344636#*#*
Make sure if you don't want to be locked into the carrier you force switched to, you need to use the "Turn On Auto Switch" code afterwards. *Auto-switching will resume after a reboot. *However, it will start with the last carrier that you were connected to before the reboot.Today 03:30 AM
LINK TO POST COPIED TO CLIPBOARD