Database Users

Nexus 6 Android 5.1 different versions discussion

We are having 3 official versions of the android 5.1 showing up. LMY47D, LMY47E, LMY47I. Some say they are carrier specific, some say they are not, and others have no idea what is going on. So, let’s discuss all the versions here and why some may or may not think that each one is carrier specific.
My main questions to those that say they are carrier specific is, I though Nexus 6 was not carrier locked and can work on all 4 carriers just by swapping the sim card. If that is the case, the how can we have carrier specific updates? I guess in theory it can be related to the sim that we have in our phones, so then by changing the sim from one carrier to another we will need to/offered the other software version?

There was a thread pointing to a twitter from someone at T-Mobile that explained this. As I understand it, Google changed the way it handles the minor network tweaking carriers need to make for their network and SIMs. Any OS would work with any phone but the carrier specific version will work slightly better. They can't make any changes to apps or the OS, just some network parameters. I'm oversimplifying but that's what I got out of it.

mgerbasio said:
There was a thread pointing to a twitter from someone at T-Mobile that explained this. As I understand it, Google changed the way it handles the minor network tweaking carriers need to make for their network and SIMs. Any OS would work with any phone but the carrier specific version will work slightly better. They can't make any changes to apps or the OS, just some network parameters. I'm oversimplifying but that's what I got out of it.
Click to expand...
Click to collapse
hmm, i need to find that.

I'll assume because of the N6's "all carrier compatibility" they have released carrier specific optimizations in their different builds. Unfortunately, and in my opinion, Google caved with the N6 to get better sales. It is what it is and I'm just thankful I have a phone that I can still do as I please with it. It would be nice, and thoughtful, if the Goog would release official information on what the heck they are doing with these different builds.... is that so hard?!

So does anyone know which one matches which carrier?

kdoggy said:
So does anyone know which one matches which carrier?
Click to expand...
Click to collapse
if its carrier specific, D is sprint, E is verizon, M is t- mobile.
edit, since canada is getting version D right now, D must be just general. Who knows. lol

So nothing specific to AT&T yet? Just curious to try a carrier specific one and see if data is faster.

stas333 said:
hmm, i need to find that.
Click to expand...
Click to collapse
Try these...
http://forum.xda-developers.com/showpost.php?p=59535507&postcount=90
http://forum.xda-developers.com/showpost.php?p=59535608&postcount=92

Not so much. 47e brought in new camera proprietary binaries too so it isn't just carrier specific

stas333 said:
if its carrier specific, D is sprint, E is verizon, M is t- mobile
Click to expand...
Click to collapse
Can't be carrier specific, I am on 3 Uk and have the D variant.
Sent from my Nexus 6 using XDA Free mobile app

I would weigh in and say that if a carrier makes a change needing a new build, it gets submitted to Google, tested and the changes only affect those with that carrier, likely due to SIM detection.
The fact that the phone has radios for all the carriers means that this can be possible, tweaks to a radio or band your phone may not use won't affect you ... and at the same time Google can toss in some tweaks across the board for all of us. I suppose that what makes it confusing is that while any of them can be flashed, they'll only push out the one to a carrier specific imei set, like E to Verizon.
For the normal user, they get an update that makes their specific network functionality better, and the others are not pushed for that, but may get the overall tweaks in the next update to their phone in general, or if before that there is a carrier requested tweak for them that requires a build release.
But we here, see all of this because we have that "wanting to have the latest build" mentality, the questions arise.

westers035 said:
Can't be carrier specific, I am on 3 Uk and have the D variant.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
What was suggested was that every build would work but a specific variant would be slightly better. For example m would be better for t mobile but any variant would work. For carriers other than sprint, verizon and t mobile I don't know if there'd be any real difference.

Has anyone on ATT received a 5.1 OTA?
If so, which one?

sykopompos said:
Not so much. 47e brought in new camera proprietary binaries too so it isn't just carrier specific
Click to expand...
Click to collapse
I knew something seemed different about the camera. Photos in low light looked better to me.
Sent from my Nexus 6

stas333 said:
if its carrier specific, D is sprint, E is verizon, M is t- mobile
Click to expand...
Click to collapse
Exactly. But some will never admit it

The real question is this:
Can someone on T-mobile who is on 47D or 47E see if they get an OTA update to 47M?
If the builds are carrier specific, would google push them based off the the SIM or the IEMI? It would have to be the SIM right? For people that purchased a phone through Google/Motorola and are using it on Verizon. Or switch networks, whatever the case may be.

buschris said:
Exactly. But some will never admit it
Click to expand...
Click to collapse
Admit what? If it it carrier specific then explain why E has Camera updates that D does not? What does that have to do with the carrier?
If everything was the same except for the Radio.img then I'd buy the carrier only thing, but there are more that's changed.

buschris said:
Exactly. But some will never admit it
Click to expand...
Click to collapse
i edited my post. D is not Sprint. It must be general version since Canada is getting it right now.

buschris said:
Exactly. But some will never admit it
Click to expand...
Click to collapse
Because its not true, then why did i get the 47D version in the Netherlands Europe. Btw i also have Sprint and Verizon files in my firmware, so that tells me they are universal roms that contain specific (network) optimisations that will be triggered when using a specific carrier.

phoenixus said:
The real question is this:
Can someone on T-mobile who is on 47D or 47E see if they get an OTA update to 47M?
Click to expand...
Click to collapse
According to the T-Mobile Support page, the requirements to upgrade to 47M is that your current build must be LRX22C, so I'm guessing that those with 47D or 47E won't be able to get an OTA update to 47M.
I'm on T-Mobile with 47D, and I didn't receive any OTA update as of now.

MPA44G is new developer preview build.... what changes do you see?

New build MPA44G is latest developer preview firmware of Android M. Maybe the last, too.
Download it here.
Source here

I haven't noticed anything so far

is there a new radio?

joeyddr said:
is there a new radio?
Click to expand...
Click to collapse
I don't think so. I did a dirty flash and everything is working

There is a thread for this
Sent from my Nexus 6 using Tapatalk

Just flashed via fb and the radio now ends in 24r

how is navigation read lte devices have a location bug

kornklown69 said:
how is navigation read lte devices have a location bug
Click to expand...
Click to collapse
Saw that as well. This is a huge bug since majority of the people use LTE while using navigation.

Is now on tap working with the newest build?

Having issues connecting to my wifi network. It connected and couple of seconds later disconnects. It says connection failure.

wera750 said:
Is now on tap working with the newest build?
Click to expand...
Click to collapse
Nope. Seems like it was all under the hood changes apart from the new boot up screen. Still no easter egg,

akhan47 said:
Nope. Seems like it was all under the hood changes apart from the new boot up screen. Still no easter egg,
Click to expand...
Click to collapse
Can someone please share the new boot animation? I have started a thread here http://forum.xda-developers.com/nexus-6/themes-apps/android-marshmellow-boot-animation-t3180825 if someone is willing to provide it...it doesn't have to be a flash-able zip, just copy paste will do...
Thank you

Someone check stagefreight detector

Enhanced data switch is back when on Project FI. Its not there in the current 5.1.1 builds.

Permissions check is working. What I mean is that an app will ask you to allow or deny permissions when if first attempts to do something. Example: I went to download something on Chrome and I received a prompt asking me to allow or deny chrome access to my music, videos, and files.

How many threads do we need for this? There is already a discussion thread.
Sent from the Nodes of Ranvier

eep2378 said:
How many threads do we need for this? There is already a discussion thread.
Sent from the Nodes of Ranvier
Click to expand...
Click to collapse
3 is the golden number.

jodvova said:
3 is the golden number.
Click to expand...
Click to collapse
Owned

Lets keep it neat, tidy and in one place
http://forum.xda-developers.com/nexus-6/general/android-m-discussion-thread-t3120782
Thread closed

cm13 not switching to anything other than wdcma only.

Hey folks , title says it all. I switched to cm13 from chroma , performed a full system wipe including sd card. So far so good but the only problem is , gsm doesn't work. I can't switch to it. Not from the settings and not from the dialer hidden menu. When i select gsm , it immediately switches back. It's always "Wdcma Only". Is this a known bug ? I scoured xda but haven't been able to find anything.
Thanks in advance.
Edit : Flashed the stock radio from 5.1.1 to no avail , also tried the 33-1.07 hybrid modem again doesn't switch. Using the latest December 27th build.

There was a bug report in the mako CM13 thread about being unable to switch between 2G and 3G, perhaps this is the same issue?
I think someones written a patch and just waiting for it to be merged.
Can you explain to me why you want to switch between them? My phone automatically switches, if 3G is available, it uses that, if its not, it drops back to the best available 2G signal automatically. Why would you choose not to use 3G if its available and just let the phone automatically switch?

Aragorn84 said:
There was a bug report in the mako CM13 thread about being unable to switch between 2G and 3G, perhaps this is the same issue?
I think someones written a patch and just waiting for it to be merged.
Can you explain to me why you want to switch between them? My phone automatically switches, if 3G is available, it uses that, if its not, it drops back to the best available 2G signal automatically. Why would you choose not to use 3G if its available and just let the phone automatically switch?
Click to expand...
Click to collapse
What you're talking about is wcdma preferred mode. Mine is stuck on wcdma only. Which means i don't have gsm so it won't switch automatically. That and the fact that i rarely use 3g because i'm always on wi-fi somewhere , using gsm saves battery. also on lollipop 3g modem took horribly long wake locks that lasted for %70 of the idle time so i hate msm.hsic.wakelock. But if it is a known bug , i'm relieved because that should be patched soon. Without me having to restore my backup. Thanks.
Sent from my Nexus 4 using Tapatalk

boltthrower56 said:
What you're talking about is wcdma preferred mode. Mine is stuck on wcdma only. Which means i don't have gsm so it won't switch automatically. That and the fact that i rarely use 3g because i'm always on wi-fi somewhere , using gsm saves battery. also on lollipop 3g modem took horribly long wake locks that lasted for %70 of the idle time so i hate msm.hsic.wakelock. But if it is a known bug , i'm relieved because that should be patched soon. Without me having to restore my backup. Thanks.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I just flashed CM13 on my wife's nexus 4 and I realized LTE wasn't enabled. Googled it and it seems there was an app for lollipop to enable it but it didn't work out for me.
Is it a CM13 bug thing or am I missing something?

pcaseiro said:
I just flashed CM13 on my wife's nexus 4 and I realized LTE wasn't enabled. Googled it and it seems there was an app for lollipop to enable it but it didn't work out for me.
Is it a CM13 bug thing or am I missing something?
Click to expand...
Click to collapse
It doesn't work for me too. I think it might be a bug
Sent from my Nexus 4 using Tapatalk

boltthrower56 said:
It doesn't work for me too. I think it might be a bug
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
It's a known bug. We have to wait for this patch to be merged. Keep an eye on it!
ht_tp://review.cyanogenmod.org/#/c/125897/
Thanks to Streetwalker for finding the bug.

TigTex said:
It's a known bug. We have to wait for this patch to be merged. Keep an eye on it!
ht_tp://review.cyanogenmod.org/#/c/125897/
Thanks to Streetwalker for finding the bug.
Click to expand...
Click to collapse
Thanks for the heads-up. I checked it , i think it hasn't been merged yet. So we gotta wait for tomorrow's release i guess.

Can anyone get their Nexus 4 running a recently nightly (like Jan 8th 2016) successfully switch to LTE? The fix in question was merged a few days ago.
Even though I can go into the *#*#4636#*#* service menu and successfully switch to LTE/GSM auto, or LTE/CDMA auto, and the radio *does* appear to power-cycle, it still says on 3G/H+ (so the status bar icon says). Never had this issue with CM12.
My build.prop also says my preferred network mode is 9, even after rebooting, which should keep it on LTE. Any ideas?

The only way to have LTE is to change that patch to include LTE instead of only GSM and WCDMA but since LTE isn't fully supported on nexus 4, a patch like that will never be merged.
Probably someone will make one "lte enabler" for cm13, just wait (or help)

Build with that patch
TigTex said:
The only way to have LTE is to change that patch to include LTE instead of only GSM and WCDMA but since LTE isn't fully supported on nexus 4, a patch like that will never be merged.
Probably someone will make one "lte enabler" for cm13, just wait (or help)
Click to expand...
Click to collapse
i saw this and since i wanted to figure out how to build cyanogenmod anyways, i went and built cm13 with the LTE included in where the patch discussed here should have added it. I have yet to test it on my device but thought people here might be interested in it.
let me know if it works out.
i would post a link, but since this is my first post it won't let me. i guess message me directly for it? or maybe someone can and then post the link here?

zachron said:
i saw this and since i wanted to figure out how to build cyanogenmod anyways, i went and built cm13 with the LTE included in where the patch discussed here should have added it. I have yet to test it on my device but thought people here might be interested in it.
let me know if it works out.
i would post a link, but since this is my first post it won't let me. i guess message me directly for it? or maybe someone can and then post the link here?
Click to expand...
Click to collapse
Shoot me a PM and I'll post it for you, assuming that's allowed (mods?).

zachron said:
i saw this and since i wanted to figure out how to build cyanogenmod anyways, i went and built cm13 with the LTE included in where the patch discussed here should have added it. I have yet to test it on my device but thought people here might be interested in it.
let me know if it works out.
i would post a link, but since this is my first post it won't let me. i guess message me directly for it? or maybe someone can and then post the link here?
Click to expand...
Click to collapse
lannister80 should be posting a link to it shortly, but i thought i would give an update that i did test it on my device last night and LTE does work with it. the normal issues of making sure you have the right modem and then changing it in the *#*#* thing. i had to change mine to LTE only first and then it would work when i changed it to LTE /gsm auto... but it does work.

zachron said:
lannister80 should be posting a link to it shortly, but i thought i would give an update that i did test it on my device last night and LTE does work with it. the normal issues of making sure you have the right modem and then changing it in the *#*#* thing. i had to change mine to LTE only first and then it would work when i changed it to LTE /gsm auto... but it does work.
Click to expand...
Click to collapse
https://www.amazon.com/clouddrive/s...D4HdJg40yFjrvcAwWa?ref_=cd_ph_share_link_copy
There's the link. Can I ask which commit this CM13 build is based on? Is this a nightly, something older, etc?

lannister80 said:
URL REDACTED BECAUSE I CANNOT POST LINKS
There's the link. Can I ask which commit this CM13 build is based on? Is this a nightly, something older, etc?
Click to expand...
Click to collapse
its a nightly, i might update it on a weekly basis maybe, i have not decided. i can only use the machine i am building it on sometimes.

zachron said:
lannister80 should be posting a link to it shortly, but i thought i would give an update that i did test it on my device last night and LTE does work with it. the normal issues of making sure you have the right modem and then changing it in the *#*#* thing. i had to change mine to LTE only first and then it would work when i changed it to LTE /gsm auto... but it does work.
Click to expand...
Click to collapse
Confirmed that this build does enable LTE. I did have to, as zachron mentioned, set the radio to "LTE only" first (which enabled LTE), and then "LTE/GSM auto", (which kept LTE enabled, and will hopefully jump down to HSPA+ or 3G when necessary). Switching to "LTE/GSM auto" first did not work (radio turned off, but came back on in HSPA+/3G mode).
I'll roam around today and see if I lose data at any time (when LTE isn't available).
Thanks @zachron!!

zachron said:
its a nightly, i might update it on a weekly basis maybe, i have not decided. i can only use the machine i am building it on sometimes.
Click to expand...
Click to collapse
@zachron: Can you show me what source changes you made? Maybe I can set up a github account and do a merge request with these changes. I can't fathom why this isn't included in CM13 for the N4xus 4 when it was in CM11, CM10 etc.
https://github.com/CyanogenMod/android_device_lge_mako/tree/cm-13.0

lannister80 said:
@zachron: Can you show me what source changes you made? Maybe I can set up a github account and do a merge request with these changes. I can't fathom why this isn't included in CM13 for the N4xus 4 when it was in CM11, CM10 etc.
https://github.com/CyanogenMod/android_device_lge_mako/tree/cm-13.0
Click to expand...
Click to collapse
sure.
https://github.com/CyanogenMod/andr...orks/base/core/res/res/values/config.xml#L234
i changed "<string translatable="false" name="config_radio_access_family">GSM|WCDMA</string>" to
"<string translatable="false" name="config_radio_access_family">GSM|WCDMA|LTE</string>"
as someone else mentioned, earlier in this thread though, they may not change it because the nexus 4 does not "officially" support lte

zachron said:
as someone else mentioned, earlier in this thread though, they may not change it because the nexus 4 does not "officially" support lte
Click to expand...
Click to collapse
Which is insane, because they absolutely allowed this in the last several major CM versions (12, 11, probably 10 and 9). Enabling LTE was one of the first things I did after getting my Nexus 4 in March 2013, and I was on an official CM build for years.
The "enabler" just messes with build.prop and makes some database changes to make the setting "stick" after reboot, so it must have been an allowed option when it was built (the enabler can't change that).
I don't know what the deal with the sudden change of heart is...

lannister80 said:
Which is insane, because they absolutely allowed this in the last several major CM versions (12, 11, probably 10 and 9). Enabling LTE was one of the first things I did after getting my Nexus 4 in March 2013, and I was on an official CM build for years.
The "enabler" just messes with build.prop and makes some database changes to make the setting "stick" after reboot, so it must have been an allowed option when it was built (the enabler can't change that).
I don't know what the deal with the sudden change of heart is...
Click to expand...
Click to collapse
yeah i dont disagree

zachron said:
yeah i dont disagree
Click to expand...
Click to collapse
Pull/merge request created:
https://github.com/CyanogenMod/android_device_lge_mako/pull/6
Hope I didn't screw it up, I'm new to git.
---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------
lannister80 said:
Pull/merge request created:
https://github.com/CyanogenMod/android_device_lge_mako/pull/6
Hope I didn't screw it up, I'm new to git.
Click to expand...
Click to collapse
Oh damn it, I have to do it via this site (they won't merge anything submitted directly on the repository):
http://review.cyanogenmod.org/

Official USA firmware appears for Z5 E6603

Just want to let you guys know that today, Sony has uploaded the official firmware for the USA version for the E6603 device. It's version 32.0.A.6.209 with a region tag of R4B. It's listed as Customized US (unbranded). This is the first time the firmware is released for a non dual Z5 device. The CDA is 1300-4290.

I'm guessing this firmware is still lollipop and not marshmallow, right?
Quick question, if I switch firmwares, would I lose my DRM keys? I have locked bootloader still and don't want to lose them. I do want to switch firmwares to US or Canada so I have a local baseband. The signal is not the best and I'm pretty sure switching firmwares will definitely help with that.

You only lose DRM keys when you unlock bootloader.

Is it 5.1.1 still?? what changes or fixes does it have??

djfranmoreo said:
Is it 5.1.1 still?? what changes or fixes does it have??
Click to expand...
Click to collapse
Yes, its lollipop ?.. And keep sucking it untill sony release marshmallow [emoji6].
No noticeable changes. All the bugs are as it was before.
Sent from my E6683 using Tapatalk

sandeep121sp121 said:
Yes, its lollipop ?.. And keep sucking it untill sony release marshmallow [emoji6].
No noticeable changes. All the bugs are as it was before.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Please, can you explain what's the point of the update then??

djfranmoreo said:
Please, can you explain what's the point of the update then??
Click to expand...
Click to collapse
battery better than before
Camera color more saturated but still noise when zooming
Phone fastest a little bit
Better wifi change from network to other
Better network change from e to 3g to lte
Also this version is Base for marshmallow update.
Sent from my E6683 using Tapatalk

does this drop the fingerprint?

Yes

sandeep121sp121 said:
battery better than before
Camera color more saturated but still noise when zooming
Phone fastest a little bit
Better wifi change from network to other
Better network change from e to 3g to lte
Also this version is Base for marshmallow update.
Sent from my E6683 using Tapatalk
Click to expand...
Click to collapse
Offcourse there's noise when zooming, that's the way digital zoom works.
If you take two pictures in a tripod stand, one zoomed and one not zoomed you can cut the not zoomed image to the same size and have two exact same images. Digital zoom is worthless, it is the exact same thing as zooming in on a pic in the gallery.

gm007 said:
Yes
Click to expand...
Click to collapse
why??

At least sony should start marshmallow concept for z5 user.
Z3 users are enjoying the concept build but z5 user are waiting.
We deserve concept build
Sent from my E6683 using Tapatalk

crazeazn said:
does this drop the fingerprint?
Click to expand...
Click to collapse
Fingerprint stop working with this update? Really has no fingerprint in US devices?

I've tried this (.209) firmware, it does remove the fingerprint option.
Was forced to go back to the older firmware to get it back ;D

ChristianLetti said:
I've tried this (.209) firmware, it does remove the fingerprint option.
Was forced to go back to the older firmware to get it back ;D
Click to expand...
Click to collapse
lolol, does that mean the US devices only have it disabled in software? Seems likely, I didn't think they'd start a new production line just to remove the fingerprint reader.
Did you notice any change in signal though?

sovanyio said:
lolol, does that mean the US devices only have it disabled in software? Seems likely, I didn't think they'd start a new production line just to remove the fingerprint reader.
Did you notice any change in signal though?
Click to expand...
Click to collapse
See, the signal was why I was looking forward to this being released but I won't trade fingerprint for better signal :/

Honestly the signal was just the same.
Although my comments could not be very accurate, since the signal around home and work is very strong.

cj1171 said:
See, the signal was why I was looking forward to this being released but I won't trade fingerprint for better signal :/
Click to expand...
Click to collapse
Agreed, but we could frankenstein a firmware if the signal is better..

sovanyio said:
Agreed, but we could frankenstein a firmware if the signal is better..
Click to expand...
Click to collapse
You need someone who got the phone to try flashing the phone with other firmware,that way you know forsure if they removed the hardware.

I think when on 8th of February someane buys officiall US variant, and if Fingerprint doesnt work, someone will just try to flash other versions, for example CE1 or other, to see if it'll work. Might be.

WiFi Assistant for Non Project Fi

I apologize if this is old news, but I just noticed that Wifi Assistant is now active for phones on carriers other than Project Fi.
Settings>Google>Networking>Wi-Fi Assistant

spotmark said:
I apologize if this is old news, but I just noticed that Wifi Assistant is now active for phones on carriers other than Project Fi.
Settings>Google>Networking>Wi-Fi Assistant
Click to expand...
Click to collapse
I'm in Canada, using an international version of the Nexus 6p, and there is not even a section called Networking under Google. I'm on the latest version of Google Play Services and Connectivity.
Could this have something to do with me being on the Developers edition of Android N before? I thought it upgraded to the retail edition when Nougat came out???
Sent from my Nexus 6P using XDA Free mobile

montrealguy said:
I'm in Canada, using an international version of the Nexus 6p, and there is not even a section called Networking under Google. I'm on the latest version of Google Play Services and Connectivity.
Could this have something to do with me being on the Developers edition of Android N before? I thought it upgraded to the retail edition when Nougat came out???
Sent from my Nexus 6P using XDA Free mobile
Click to expand...
Click to collapse
I'm on RomShake, so maybe it has been there since I installed 7.0, and I just didn't notice until now.

montrealguy said:
I'm in Canada, using an international version of the Nexus 6p, and there is not even a section called Networking under Google. I'm on the latest version of Google Play Services and Connectivity.
Could this have something to do with me being on the Developers edition of Android N before? I thought it upgraded to the retail edition when Nougat came out???
Click to expand...
Click to collapse
I'm still using PN/M rom and it is showing under google/network. You may need to wait for Google to update your google connectivity services app or go to apkmirror.com to update it yourself.

It's being turned on in waves. Keep checking.

montrealguy said:
I'm in Canada, using an international version of the Nexus 6p, and there is not even a section called Networking under Google. I'm on the latest version of Google Play Services and Connectivity.
Could this have something to do with me being on the Developers edition of Android N before? I thought it upgraded to the retail edition when Nougat came out???
Sent from my Nexus 6P using XDA Free mobile
Click to expand...
Click to collapse
You can also access the setting under Settings/Wi-fi/Gear icon (not the 3-dot menu)

Caltinpla said:
I'm still using PN/M rom and it is showing under google/network. You may need to wait for Google to update your google connectivity services app or go to apkmirror.com to update it yourself.
Click to expand...
Click to collapse
spotmark said:
I'm on RomShake, so maybe it has been there since I installed 7.0, and I just didn't notice until now.
Click to expand...
Click to collapse
breezeli said:
It's being turned on in waves. Keep checking.
Click to expand...
Click to collapse
wvcadle said:
You can also access the setting under Settings/Wi-fi/Gear icon (not the 3-dot menu)
Click to expand...
Click to collapse
Ok this is getting really weird. It does not appear under Settings/Wi-fi/Gear. And Networking doesn't even appear under Settings/Google.
1. I thought it could be because I was still on NRD90M, so I used the Toolkit to upgrade the OTA to NRD90U. It still didn't show up. Are you guys all on custom roms ? I'm wondering if this is why you are all getting it.
2. So then I used http://opengapps.org/ to create a gapps zip of the latest Google apps and installed it. And it STILL DOESN'T SHOW UP! Furthermore, I checked and Google Fi and Android Pay don't show up in my app list, even though they show up under Settings/Apps as Disabled.
Am I doing something wrong here?

montrealguy said:
Ok this is getting really weird. It does not appear under Settings/Wi-fi/Gear. And Networking doesn't even appear under Settings/Google.
1. I thought it could be because I was still on NRD90M, so I used the Toolkit to upgrade the OTA to NRD90U. It still didn't show up. Are you guys all on custom roms ? I'm wondering if this is why you are all getting it.
2. So then I used http://opengapps.org/ to create a gapps zip of the latest Google apps and installed it. And it STILL DOESN'T SHOW UP! Furthermore, I checked and Google Fi and Android Pay don't show up in my app list, even though they show up under Settings/Apps as Disabled.
Am I doing something wrong here?
Click to expand...
Click to collapse
It's a server side thing. All you can do is make sure that your have the latest Google Connectivity Services update and wait. I have had this Wi-Fi assistant toggle for a few days on official rooted 7.0 on my 5X.
Sent from my Nexus 5X using Tapatalk

@SlimSnoopOS & @montrealguy
I am having similar issues to montreal, the difference with me is that I originally had the networking menu under settings>google>networking. But the connectivity manager would always force close on me when I tried to enable it. I thought it might have been a problem with the permissions or having root, I toggled root off w/ magisk and uninstalled google connectivity services and then reinstalled it. Now, the networking option is completely gone from my menus.

ErikFry said:
@SlimSnoopOS & @montrealguy
I am having similar issues to montreal, the difference with me is that I originally had the networking menu under settings>google>networking. But the connectivity manager would always force close on me when I tried to enable it. I thought it might have been a problem with the permissions or having root, I toggled root off w/ magisk and uninstalled google connectivity services and then reinstalled it. Now, the networking option is completely gone from my menus.
Click to expand...
Click to collapse
Are you using a theme?

SlimSnoopOS said:
Are you using a theme?
Click to expand...
Click to collapse
Substratum navbar theme. Nothing else. I'll probably just have to reflash everything.

ErikFry said:
Substratum navbar theme. Nothing else. I'll probably just have to reflash everything.
Click to expand...
Click to collapse
Might try without the theme just to rule that out. Themes are sometimes responsible for various system FCs from what I've been seeing recently.
Sent from my Nexus 5X using Tapatalk

It's in at least the Ontario OTA 7 update...