Hi everyone,
I am using my brand new Nexus 6p for 3 weeks. I changed my mobile connection type to LTE at first but since last week it always changes to 3g again by itself.
I turn on wifi and turn off mobile data while LTE but after enabling mobile data and turning off the wifi it changes to 3g again.
I changed the settings in *#*#4636#*#* to LTE only but still it changes.
How can i fix this problem?
I am on Verizon and had the same problem. I called support, they had me try a few things
that didn't work. They ended up sending me a new sim card. When it got here, I called them to activate it. Had to use a Verizon phone but once it was put it in my 6p it has been on LTE every sense.
Sent from my Venue 8 7840 using XDA Free mobile app
What build number are you on?
nathanchance said:
What build number are you on?
Click to expand...
Click to collapse
It's MHC19I
Sent from my Nexus 6P using XDA-Developers mobile app
Did the April update (MHC19Q) fix this for you? I'm still seeing this issue with the latest release on t-mobile US, however I drop down to Edge, not LTE
Fwiw, I had this issue terribly up until recently when I temporarily flashed the n preview (using the fastboot, flash-all command).
Upon clean flashing back to an up to date M build (latest PN) the issue is gone. Not sure if some system corruption or what caused it but if you look around online there's a ton of reports of the same thing. Toggling airplane mode is usually a temp fix.
Seeing this issue on t-mobile. It looks like it relates to the new band (12) that was recently added. If I have radio firmware that support band 12 then I can't connect, but if I go back to an old image (MDB08K) then I can get onto the older band 4 on t-mobile.
Related
Hey,
I updated my phone about 5 days ago to the latest 4.3 and since then I've lost my 3g connection. It has been there a bit but today it's completely gone and hasn't come back.
Tried turning it on/off, switching to airplane, changing from WDCMA to GSM and running in dafe mode. Nothing works.
Does anyone know what the issue is and how to solve it?
I should point out I'm not very tech savvy and don't know all the lingo so go easy on me
Thanks!
Post a screenshot of Settings > About Phone and scroll to the bottom. Is your phone stock or rooted?
Check your APN under mobile networks. Make sure you have an APN .
Sent from my Nexus 4 using xda premium
First the basics. Nexus 6p received 3/30. I did NOT turn it on and update it to the latest stock firmware before proceeding. Rather I immediately unlocked bootloader, installed TWRP, installed CM13 and GApps Nano from OpenGApps. Running on T-Mobile's network using a cut down Micro SIM from my Oneplus One down to Nano size.
I'm running the latest CM13 release snapshot, ZN0EAO1T5, and my mobile data will work initially with LTE upon boot or restart. After a short time (minutes) it will no longer have a data connection. Calls and SMS still go through. While the data is active, if I turn on Wifi and then later return to mobile data the data is not active. In the status bar it just has the triangle signal icon without any indication of type of data connection (i.e. LTE, HSPA+, 3G, etc.). When I pull down the quick setting menu it does list LTE on the mobile connection quick setting button.
Additionally, MMS does not work no matter what I do. Mobile data connection or Wifi. I've researched the T-Mobile APN settings thinking this could have been the issue and no editing there changed anything.
I will likely try to restore to current factor images and begin again to see if that helps. I'll probably go get a proper Nano SIM from T-Mo today too just in case there is any issue along that front.
Anyone else experience this? Anyone else run across others having this issue? It seem separate from the 6.0.1 issues I witnessed with stock ROMs while searching but perhaps I'm wrong.
Currently installing most current stock image and then will try again. Noticed the bootloader and radio were older versions. Hopefully restarting from scratch with the newest system will solve these issues. Fingers crossed.
Boom! Working!
Restarted from scratch after flashing the most current stock ROM. All Set. Thanks for all the help!
... Spoke too soon.... Same problems are right back. I think it may be related to this workaround to stop some of the error messages:
http://forum.xda-developers.com/nexus-9/development/fix-build-prop-variety-fix-aka-contact-t3133347
I ran this to get rid of the error and I think that caused the problem. So I tried to re-flash only the vendor.img as I've read that as a fix to a few things and it did not help.
I'll have to start from scratch again and see if I'm right. Clearly there is something I'm doing causing this. I just can't figure out what...
AFWall+, Adaway, CM13 superuser, Privacy Guard ??? Ugh.
You don't think it's from the cut down sim getting damaged?
Sent from my Nexus 6P using XDA-Developers mobile app
frigidazzi said:
You don't think it's from the cut down sim getting damaged?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry I did not update this sooner.
No, that is not that issue. I did end up determining that the problem is AFWall. There is, apparently, some changes in marshmellow that the developer, ukanth, needs to update AFWall to work with it more appropriately. So I've disabled AFWall for the time being.
I'm not programmer/developer, so it just seems to me to be related to this: https://github.com/ukanth/afwall/issues/520
ukanth notes in that thread this will be fixed in the next update.
I was able to get 100+mbs on LTE in a few different places, so definitely not that SIM.
Sent from my Nexus 6P using XDA-Developers mobile app
stewa2jm said:
Sorry I did not update this sooner.
No, that is not that issue. I did end up determining that the problem is AFWall. There is, apparently, some changes in marshmellow that the developer, ukanth, needs to update AFWall to work with it more appropriately. So I've disabled AFWall for the time being.
I'm not programmer/developer, so it just seems to me to be related to this: https://github.com/ukanth/afwall/issues/520
ukanth notes in that thread this will be fixed in the next update.
I was able to get 100+mbs on LTE in a few different places, so definitely not that SIM.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
You can try the 2.50 radio as well. I was getting similar issues with the latest radio on a variety of roms until I downgraded to that radio. Now I don't have any service issues at all.
messiahfreedom said:
You can try the 2.50 radio as well. I was getting similar issues with the latest radio on a variety of roms until I downgraded to that radio. Now I don't have any service issues at all.
Click to expand...
Click to collapse
Thanks for the suggestion. If AFWall isn't updated soon I'll try it out. I've noticed quite a large increase in data usage already this month without AFWall.
Sent from my Nexus 6P using XDA-Developers mobile app
stewa2jm said:
I did end up determining that the problem is AFWall.
Click to expand...
Click to collapse
You're a saviour man. Was plagued by the data connection issue since yesterday and happened to stumble upon this thread. Disabled AFWall+ and the data started working properly. Thanks a lot for the help man. :good::highfive:
inimaitimepass said:
You're a saviour man. Was plagued by the data connection issue since yesterday and happened to stumble upon this thread. Disabled AFWall+ and the data started working properly. Thanks a lot for the help man. :good::highfive:
Click to expand...
Click to collapse
I had to abandon afwall some time ago due to all of this. Now I'm running CopperheadOS, which is not rooted, so cannot use it anyway. Android 7.* has some decent settings to control permissions by app anyway, so afwall doesn't add enough for me to worry about it anymore.
Sent from my Nexus 6P using Tapatalk
I'm gonna make a post here since NOTHING seems to be working. I'm a T-Mobile customer. Yesterday, I purchased a great condition nexus 6P from someone because my LG G5 is cracked and I was getting tired of it anyway so I opted to just buy a nexus instead of using my insurance on that phone. Everything is all good except for one major issue. VOLTE and WiFi calling just refuse to work with my sim in the Nexus.
I've called T-Mobile twice. I've factory reset from back up and reset settings twice. I've hard reset from stock recovery once. I've wiped network settings and restored default apns. I've manually changed the apns from what I see on Google, reddit and here. I've copied my apns from my LG G5 where VOLTE and wifi calling work perfectly fine. I've cleared cache. I've cleared the cache of the project fi and hangouts apps just in case there's something left over from the previous owner. I've gone into the *#*#4636 menu and tried a bunch of different stuff several times but no matter what I absolutely can not get wifi calling or VOLTE to work with TMobile on my nexus 6P. LTE it's self works perfectly fine for data.
Yes, all settings for wifi calling and enhanced LTE calling and VOLTE are turned on lol. I've tried the trick where you toggle wifi preferred on and off and restart the phone. Nothing happens. I don't even get a wifi calling reg error. It never shows as active in the data toggle in the quick settings are nor the status bar or dialer. It just isn't active. Same for VOLTE. I AM getting band 12. I can see it in the LTE discovery app. VOLTE just isn't working though. Whenever I make a call I can see LTE switching off and it switches to HSPA therefore making calls really difficult in my shoddy signal area at my house which is why I really need it to work.
I'm fairly certain I can root and install a ROM which will fix these problems but I don't own a PC. . I thought MAYBE the previous owner had previously had the phone rooted and tinkered with something somewhere that may have messed something up but that doesn't appear to be the case. Bootloader is locked and recovery is stock.
Can anybody help and tell me what in the world is going on here? I don't want to have to sell this nexus and revert back to my cracked screen G5. I would just switch carriers but I still owe money on the G5 so I was just gonna ride it out til I payed it off.
O and one last thing, after scowling google and forums for hours on end yesterday and today I did see one post mentioning something about this stuff being related to IMS provisioning and settings which are tied to a phones IMEI on T-Mobile and not the sim card and how that person simply called T-Mobile and got a hold of wifi calling technical support who was clueless but created a ticket for him and within 72 hours the issue was resolved. OK well I did the same exact thing and they refuse to create a ticket for me because it's not a T-Mobile phone and because according to them they are not allowed to create a ticket because wifi calling works fine in my G5 and therefore it's the phone and not them or their network lol. What a crock. I'm willing to bet if I put the sim in another unlocked phone with 7.1.1 and wifi calling fully available that it isn't going to work either. There's some sort of communication error going on between the sim being in this phone and their network it appears.
Check these screenshots out. T-Mobile is clueless
http://imgur.com/5MuO34s
http://imgur.com/XVd8CdA
http://imgur.com/uUGN3ae
http://imgur.com/cfYxfqh
I can only suggest;
1) Find a PC and re-flash the latest factory images from Google. Both "fastboot flashing unlock" and "fastboot flashing lock" will wipe all data, so backup first. Also confirm it fully boots correctly after flashing before you re-lock the bootloader.
2) Get a new 3-in-1 SIMM from T-Mobile. You can use their web site to switch cards and give it 24 hours to be fully provisioned.
3) Confirm your E911 address is correct on T-Mobile's site and wait 24 hours after any changes for Wi-Fi calling to actually start working.
I HAVE THE SAME EXACT PROBLEM AS YOU POSTED!!! GONE THRU THE SAME PAIN. LOL I'll attempt the ticket thing to see if I get anywhere. Did you ever get it resolved?
EDIT:
My theory is that since the phone was used in Project FI, they specifically turn off this feature in the back end for the specific phones, by Imei or something since project FI uses T-Mobile as well.
EDIT 2:
they wont' create a ticket for me either. I guess I will just have to ride it out.
EDIT 3: I FIXED IT!! NEXUS 6P VOLTE AND WI-FI CALLING FIX T-MOBILE
I flashed back to android 6.0 Build#: MMB29N (I used the Nexus ToolKit 2.1.9: google it. BTW, your phone will be wiped, so backup first) VOLTE just started working with this version of android 6.0. Then I upgraded using the OTAs and now i'm on 7.1.1 build#: N4F260 with VOLTE and Wifi calling working as it should! I hope this helps someone out there!
For what it's worth, reverting to the build you mentioned fixed it for me on my two Nexus phones coming from Project Fi to T-Mobile as well! Thanks for the help!
You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.
banancanard said:
You only need to install the radio from build MMB29N. I did this by downloading the build from the android website. Extract the radio from the zip and install it (I used nexus root toolkit but you can also just use flashboot if you wanted). This means you don't even need to revert your image and lose your data.
Click to expand...
Click to collapse
wish I had seen this sooner. cheers!
Had the exact same issue and this fix worked for me. Wasted a couple of hours with T-mobile (they were actually very helpful and debugged everything on their end to confirm the provisioning was good) and then 2+ hours with Google support. Actually had already filed for a device replacement which I canceled after finding this post.
I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?
k2kevink2 said:
I'm so glad I found this thread - my VoLTE and WiFi calling has not been working on T-Mobile and I'm anxious to give this a try. Numerous phone calls and support tickets with T-Mobile haven't resolved the issue. I don't know much other than how to follow detailed directions. My phone isn't rooted and bootloader is locked. I'm on Android version 7.1.2. Is there a way for me to install the MMB29N radio on my Nexus 6P without losing my app data given that my bootloader is locked?
Click to expand...
Click to collapse
Flashing the radio -sadly- requires an unlocked bootloader.
Did you resolve your problem?
In android 7.1.2 did you notice in Set preferred network type is set at " LTE/GSM/CDMA auto (PRL) "? 7.1.2 has been giving me issues with sms/mms. I noticed Android 6.0 has this set to correct T-mobile bands.
All works for me in 7.1.2. Make sure you don't download the Verizon version of the stock ROM. That was my issue why I couldn't have volte and Wi-Fi calling
So, when I woke up this morning I noticed my cell signal strength icon was one I haven't seen before. I tried rebooting and toggling airplane mode. I also verified that my sim is working in another device. I attached a screen cap with the icon.
Noticed something similar with mine. I had to turn wifi off, restart to get LTE data (verizon) then turn wifi back on. If restarting with wifi on the LTE data doesn't register.
that didnt work for me
update: had to factory reset, looks like verizon doesnt like that essential ph1 wont take all their bloatware, etc. might have to return the phone if this keeps up
My data connection has also become very erratic - and I've lost voice+data (VoLTE connectivity) wholly yesterday. Worked fine with the activated SIM from my HTC 10 from the 31st to yesterday.. Now, not at all, I've not been able to restore it since.
Really don't want to return it, as I really like the phone, but this has nexus 5x issues written all over it for long term use...
Hoping essential can get a certification and an agreement with Verizon before my return window is over (or at all)..
Pretty disappointed in Verizon here.
Sent from my PH-1 using XDA Labs
Same here, another issue is that essential shipped my phone and within a day i had an email from essential saying that verizon certification is still in progress. verizon will probably not certify it with their system unless essential lets them install their monitoring crap all over the phone.
j1999t said:
Same here, another issue is that essential shipped my phone and within a day i had an email from essential saying that verizon certification is still in progress. verizon will probably not certify it with their system unless essential lets them install their monitoring crap all over the phone.
Click to expand...
Click to collapse
The Nexus 6P didn't have the bloat and worked fine.
My PH-1 works fine including Enhanced 4G LTE Mode.
What do you have selected for network type?
I have the first one selected because that's the only one that includes the various CDMA protocols, EVDO and LTE.
I see the same connectivity that I had with my Nexus 6P.
i have global selected, as it covers everything the phone can connect to. i had the first one selected but it wouldnt show the lte+, just regular lte. i also have Enhanced 4g lte mode on. it just happened to lose service earlier today. if it does it again, ill probably return it after a visit to vzw
tech_head said:
The Nexus 6P didn't have the bloat and worked fine.
My PH-1 works fine including Enhanced 4G LTE Mode.
What do you have selected for network type?
I have the first one selected because that's the only one that includes the various CDMA protocols, EVDO and LTE.
I see the same connectivity that I had with my Nexus 6P.
Click to expand...
Click to collapse
I have the same settings as you, I had functional "enhanced 4G LTE" for the first 4 days as well... That ended yesterday morning abruptly, and I'm not able to bring it back.. There's more happening here.. How long has your device been on the Verizon network? Only a hunch - in a few days you won't have "enhanced 4G LTE" either, even though it'll still be checked, and provisioned for it.
Sent from my PH-1 using XDA Labs
Cellular network is not available
After 7 days my phone won’t make calls I can only use data I’m on sprint and it was working fine until today I call sprint they had no answers at all I email essential no answer now I can only use WiFi calling while home and axx out at work
So, upon further digging I found a place to look at some more in-depth stuff relating to signal stuff. I did some fooling around and switched it from unknown to lte/cdma/umts auto (prl) and it seemed to work after a few moments of time. Though it seems have gone back to t he unknown state again but is working normally for me now, so maybe it was changing states and then a reboot?
How I got to this screen was by punching *#*#4636#*#* into the dialer, and went to phone info
I'm having a similar issue. I often lose my signal. I will have the full triangle/bars but no label of the signal(LTE+/LTE/3G/1x/etc....) and no cellular data at all.
The only way I can get it to return is to restart the device. Happens a few times a day, can't be 100% sure why, but it often appears to be when switching from WiFi -> Cellular only.
I have Verizon, I have had a Nexus 6 and then a Pixel XL for the past 3 years, never once had this issue.
I had constant disconnects and lost of service with my Tmo sim. Tried my Xfinity (VZW) sim and it was great until this morning. Complete lost of service. Airplaned mode on and off, connected to old school RTT 1x.... lol This phone's cellular just plain suck for a lot of us regardless of carrier. Not sure if we just have bad phones because apparently there are those who claim they have great service and connection.
I'm having this problem with Verizon. Seems like if I'm on wifi for a long period it only connects to 1x and putting in airplane mode and stuff won't get it to re-connect to to LTE. Only a reboot seems to fix the problem.
fade79 said:
I'm having this problem with Verizon. Seems like if I'm on wifi for a long period it only connects to 1x and putting in airplane mode and stuff won't get it to re-connect to to LTE. Only a reboot seems to fix the problem.
Click to expand...
Click to collapse
Necro post here but chiming in that I have the same problem with Verizon LTE. Happens when I'm moving long distances in car too. Suddenly just drops LTE and only a reboot will bring it back.
defTwitch said:
Necro post here but chiming in that I have the same problem with Verizon LTE. Happens when I'm moving long distances in car too. Suddenly just drops LTE and only a reboot will bring it back.
Click to expand...
Click to collapse
You might check out my post from the Oreo Beta thread... I was having some goofy signal issues early on which I've pretty much cleared up by doing what I mentioned here. Someone touched on it briefly earlier but only mentioned monkeying around with the settings, said nothing about picking up a new PRL.
I state this in that post too, but just in case: I offer this with no express intent of warranty, if you screw up your device, it's on you.
https://forum.xda-developers.com/es...-oreo-beta-program-live-t3705133/post74920423
I just changed it from global to LTE/WCDMA and I got LTE back almost immediately. Was weird and global had been working for me for awhile now so not sure what happened in the past few days...
wolfhelm said:
You might check out my post from the Oreo Beta thread... I was having some goofy signal issues early on which I've pretty much cleared up by doing what I mentioned here. Someone touched on it briefly earlier but only mentioned monkeying around with the settings, said nothing about picking up a new PRL.
I state this in that post too, but just in case: I offer this with no express intent of warranty, if you screw up your device, it's on you.
https://forum.xda-developers.com/es...-oreo-beta-program-live-t3705133/post74920423
Click to expand...
Click to collapse
I had, right after writing this, tried *#*#4636#*#*
I set it to global as instructed in another post. The next time I drive a distance in the car I'll have to see if I have the same issue that only a reboot would fix again.
Thanks
I had the same issue and I resolved it a little differently than the previous posters. I turned on adb debugging and logged into adb shell and user-disabled com.redbend.app. This stops the Sprint oma-dm service from running. After doing this I no longer have the issue of my device not reinitializing lte after sleep or 3g.
I have essential on vzw but my only issue is my device won't connect to 4G. If I change network to LTE I get full 4G service but I'm unable to make phone calls. Went into vzw store and they told me you didn't get the phone from us so we cant help you. Day 14 fml
On Xfinity mobile, I had similar issues. Great LTE but sometimes calls just don't work at all. I mess with various settings and it'll work for a bit then so again. Gave up and ported over to Sprint for the free unlimited year which is still probably not worth it. Should've kept with Xfinity Mobile. Lol
Don't think it's same issue as ppl lte issue but my s10+ 1tb doesn't connect to the mobile data when u are out of wifi range. I have to either reset the phone ornl on and off airplane mode to get the data back. Seem to work if I manually disconnect the wifi rather than let it out of range.. seem to only happened after last 2 updates. Phone was purchased from Samsung on Rogers Canadian firmware anyone else?
wai_lai416 said:
Don't think it's same issue as ppl lte issue but my s10+ 1tb doesn't connect to the mobile data when u are out of wifi range. I have to either reset the phone ornl on and off airplane mode to get the data back. Seem to work if I manually disconnect the wifi rather than let it out of range.. seem to only happened after last 2 updates. Phone was purchased from Samsung on Rogers Canadian firmware anyone else?
Click to expand...
Click to collapse
Im seeing the same exact thing with my 1tb pre order purchase. Bought directly from Samsung for Verizon. I also notice terribly slow download upload speeds(4gb down/2 GB upload) when in restart the phone it will go back to 100gb+ down for a while then get stuck at 4gb again. I've factory reset the phone and odined back to asd7... still the same. I had Verizon give me a new sim and do their provisioning on their end but no improvement.
I hope its not the same hardware issue others are facing.
I just sent mine in for repair. Mine would work only on LTE band 12. If it connected to bands 2 or 4 I couldn't get text, mms, calls or the internet. It looked like it was working until I tried to do something. I downloaded Signal Spy and it showed me what band I was on. Once I figured out the bands it dint work on I had to go into the service menu and trurn them off. No more issue except data speeds were so slow! My phone was manufactured in February so I think that has something to do with it.
It's funny, Samsung kept saying it's the network and an update was coming to fix it. It never came. I even switched networks and the same issue.
Sent from my SM-G975U using Tapatalk