Well I think I have tried just about everything, but I thought I'd check first to see if anyone else has ran into this and fixed it.
Yesterday my S5 just decided it didn't want to connect to the VZW network anymore. I was running Alliance ROM at the time, but I Odin'ed back to complete stock and it is still not connecting. Wifi, bluetooth, etc. all works fine though.
I took my SIM card out and put it in my wife's S4 and it connects fine so it's not my SIM. I tried reseating my SIM about 20 times and still no love.
Any thoughts?
I'm having a similar issue. Had my s5 for a week now and it keeps dropping data whenever it feels like. Then comes back on randomly I'm going to swap it out for another one. If the new one still bad I'm going back to my trusty s4 (need to replace digitizer)
Sent from my SM-G900V using Tapatalk
I have a problem with my 6p where the signal just drops to nothing (Looking for service) and 3 or 4 seconds later it reconnects to a good LTE connection. The problem is not my connection as I live in a good area. I was rooted with xposed but for ****s and giggles I went back to complete stock and it is still happening.
I have reset the APN settings to no avail. Is this a thing that is known to this phone? Should I get a replacement? It started just recently it seems as I have had this phone since launch.
What sucks is, is that this phone is absolutely perfect (or was) and I dont want to get sent a phone with screen issues.
EDIT: I ended up getting an RMA and everything is hunky-dory.
holmgren said:
I have a problem with my 6p where the signal just drops to nothing (Looking for service) and 3 or 4 seconds later it reconnects to a good LTE connection. The problem is not my connection as I live in a good area. I was rooted with xposed but for ****s and giggles I went back to complete stock and it is still happening.
I have reset the APN settings to no avail. Is this a thing that is known to this phone? Should I get a replacement? It started just recently it seems as I have had this phone since launch.
What sucks is, is that this phone is absolutely perfect (or was) and I dont want to get sent a phone with screen issues.
Click to expand...
Click to collapse
What radio version are you on? You can flash a different version in fastboot and see if it helps.
murphyjasonc said:
What radio version are you on? You can flash a different version in fastboot and see if it helps.
Click to expand...
Click to collapse
Im on the newest one. Do I just extract it out of the 6.0 image file and just flash it over the top of the existing one?
I forgot to also mention that I tried getting a new SIM card from Verizon but that did not fix it either.
holmgren said:
Im on the newest one. Do I just extract it out of the 6.0 image file and just flash it over the top of the existing one?
I forgot to also mention that I tried getting a new SIM card from Verizon but that did not fix it either.
Click to expand...
Click to collapse
Yeah. Extract it and flash it over the top in fastboot.
Did you ever find a remedy for this problem? I'm having the same issues on t-mobile so its definitely not network or a similar related issue. Did flashing the radio from the 6.0.0 rom fix the issue? I already tried several different 6.0.1 radios and a radio from 7.0 but to no avail. I'm about to try it and if it doesn't work I'm getting rid of this phone.
I'm going to assume you mean you'll be on LTE for the longest time then all of a sudden signal completely drops then comes back on, but without the LTE signal showing near the bars, so you'll have to airplane mode, then switch mobile data on and off, then do a restart. If this is the case. That has been a documented CM13 issue for the longest time. I had the same issue with the HTC M8...
Sent from my Nexus 6P using Tapatalk
jxcorex28 said:
I'm going to assume you mean you'll be on LTE for the longest time then all of a sudden signal completely drops then comes back on, but without the LTE signal showing near the bars, so you'll have to airplane mode, then switch mobile data on and off, then do a restart. If this is the case. That has been a documented CM13 issue for the longest time. I had the same issue with the HTC M8...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am on LTE but as the OP said the signal randomly drops completely for 4-5 seconds them comes back LTE and all. I don't have to reboot or anything. This doesn't have to do with cm13 though, I've tried flashing back to full stock and I still have the problem there too.
Sent from my Nexus 6P using XDA-Developers mobile app
Damn man...I have no idea - possibly radio like the guy above my post mentioned. Wish I were of better assistance.
Sent from my Nexus 6P using Tapatalk
I've managed to get a logcat at almost the exact time the signal drop happens, I had to put it in a Zip since the Txt document was too big for the thread. The drop happened in the last couple minutes. I'm hoping someone here with more experience than me can help me solve this issue. Thanks in advance.
Having the same issue on T-Mobile smh... it gets annoying at times!
Sent from my Nexus 6P using XDA-Developers mobile app
Same problem here. On Verizon
Anyone find a fix? I'm on the latest Android N Beta on Tmobile and still have the issue.
I was just wondering if anyone else has problems with their LTE dropping to 3G out of the blue. This happens when I am at home in a really strong LTE area. My wife's Nexus 6 doesn't do this, it stays in LTE. This only seems to happen to me when I am at home.
I am running the latest PN ROM, latest vendor and gapps, and I have tried numerous kernels. Both my wife and I are using the Verizon sim through Straight Talk.
Thanks for any help or ideas you might have.
Sent from my Nexus 6P using XDA-Developers mobile app
kclive said:
I was just wondering if anyone else has problems with their LTE dropping to 3G out of the blue. This happens when I am at home in a really strong LTE area. My wife's Nexus 6 doesn't do this, it stays in LTE. This only seems to happen to me when I am at home.
I am running the latest PN ROM, latest vendor and gapps, and I have tried numerous kernels. Both my wife and I are using the Verizon sim through Straight Talk.
Thanks for any help or ideas you might have.
Click to expand...
Click to collapse
I've made a post that mentioned this. There is a issue affecting only the Nexus 6p Phones. Google supposedly fixed the issue. Although Some seems are still having issues. Apparently it's stemming from the GPS. They have a workaround that's helping some. Have your carrier clear your location, disable your GPS, Reboot phone. Uninstall updates for Google connectivity services, and try to update it. And again reboot.
I continued having issues even though they fixed it, so I went cleared out system reflashed stock images, rebooted, via mskip toolkit. Been running pure stock except root, and been working fantastic with no issue. Hope this answers your question. Good Luck!
This has happened to me like... Once or twice since I've owned my 6P (~7 months) on Verizon (Non-MVNO VZW). Flopping airplane mode, Forcing the modem to reassociate would get it to jump back on LTE. The issue I've had more frequently (20-30 times since purchase) is the phone just falling off all data completely.
If VZW LTE coverage in your area is good (It's insane here in Florida) I'd recommend trying forcing LTE only.
Dial *#*#4636#*#* from the phone dialer. Then under the "Phone Information" menu. Hit the drop down that should currently say "LTE/CDMA/UMTS Auto (PRL)" and set it to LTE.
This is going to cause one of two things.
1. It'll fix your problem, Meaning it was actually some kind of provisioning/priority issue. Your phone for some reason couldn't hang on LTE, So it fell back to 3G to maintain connectivity. Even though it would've worked if it would've tried LTE again.
2. You'll still fall off LTE. But this time, Instead of falling to 3G, It'll disconnect completely.
If it ends up being #1, I'd try swapping SIM's with your wife for a day or so, Just to see if it follows the phone or the sim card.
Just started having this issue yesterday.
Before that almost never.
I also just upgraded to the August security path.
Well my calls dropped out 3 times, On Oputs network Here in Austrlia and i was on 3G and good signal, Lastest Pacth and Stock anroid.
Hello guys. I have an a Verizon S7 currently being used on Metro PCS. I'm still running 6.0.1 Marshmallow and hoping I wouldn't have to do any software updates until a few days ago. I suddenly began getting a "sim card error" when I tried dialing out. I took out sim card, popped it back in and same issue. I even checked the sim and tray for any damage and there is none. Also, the phone has never been exposed to any liquid at all. I tried a soft reset, still same issue. Tried clearing cache in recovery, same issue still. Finally did a full wipe, set up as a new phone without doing the 7.0 update. That hasn't cleared the issue. I still can't dial out, HOWEVER people can still call me and the calls go through normally. I can also send texts. This isn't happening only in low signal areas as I initially thought. I'll have full bars in some places and not be able to call out. I don't really want the 7.0 update since I like the way my phone is now on MM. Are there any other options for me at this point? I did some research and it looks like people are relating this to a software issue which would mean I'd have to take the plunge into Nougat...
Unless anyone here can offer an alternative? :fingers-crossed:
As an added bonus, does anyone know if my mobile network settings (GSM/CDMA, GSM, UTS, etc) have something to do with this? Thank you for any suggestions!
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Dirtydcs said:
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Click to expand...
Click to collapse
Sorry for late reply. What's AP?
Dirtydcs said:
I have g930v on metro pcs, I updated. Flashed AP & rooted & out worked fine
Click to expand...
Click to collapse
By the way I ended up taking my sim card out and put it back in. It worked fine. Just yesterday it did the sim error again so it reminded me of this thread
Try going into b recovery mode and wipe cache. I did that &it fixed my calling.
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked.
I flashed several different images to no avail.
Advice?
locolbd said:
Is anyone having this issue.
I upgraded to android 8.0 and no longer able to get any Verizon LTE service no matter what location I am in. I get frequent notifications stating I am Roaming and my phone is not rooted and the bootloader was locked, yet Android Pay Pop ups stating it cannot work on my 6p because my phone is either rooted or the bootloader is unlocked. I flashed several different images to no avail. Advice?
Click to expand...
Click to collapse
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
v12xke said:
Reset Network settings reset, wipe cache partition. When you say you flashed images, do you mean sideloading OTAs.... or are you unlocked and using full images? Your post led me to believe you were getting erroneous messages about being rooted/unlocked (meaning you were not).
Click to expand...
Click to collapse
Tried it all.
I installed several full factory image versions, locked the boot-loader and then started up the phone. With the boot-loader locked and phone not rooted Android Pay still gave me the error that my phone is running a custom ROM, the boot-loader is unlocked or the phone is rooted.
I have also installed several OTA images and none of the problems I mentioned in my earlier post went away. The only way for me to get Android pay to work is to unlock the boot-loader and root the phone with magisk. However, I still get intermittent Roaming notifications, intermittent signal lost and no LTE whatsoever.
Today:
I called Google and and did 45mins of troubleshooting, the final thing we did was reset my phone and then the agent acted helpless when nothing resolved the issue.
I called Verizon did 30 minutes of troubleshooting with them, reset network setting about 100 times, turned off my phone so that they could re-provision on their end. Turned the phone on and got LTE signal for approximately 60seconds. Then it went back to 3G, then no signal and then the dreadful roaming notification every few minutes.
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
mojorisin7178 said:
Are you using the stock recovery or TWRP? And when you installed factory image did you do it through your computer using flash all? Or did you just install the factory image? Personally what I would do if wipe everything out and use your computer to install the latest factory image using the flash all script. So you are completely stock then relock the bootloader. Then you should be completely up to date with modem bootloader recovery vendor and rom. Your lte issue sounds like a modem problem possibly. And the September security patch broke safety net check and therefore Android pay. That build ended in.017. there is a new one up that fixes those issues and I think also the issue with the phone choosing mobile data over WiFi when it should be choosing wifi over mobile. That build ends in.019. try installing that build like I said above. Good luck
Click to expand...
Click to collapse
I wiped DATA so there were no files on my phone.
Downloaded july,august,september factory images and flashed, locked bootloader and tested each image to no avail. I saw the build on the google forum for 019 so i flashed that as well and same sh:silly:t different day.
Last thing I did was to flash 7.1.1 and that did not resolved my problems. Got the OTA notification to install 8.0 hoping all my problems might disappear but they did not.
It has been an hour and LTE seems to be working again
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Wow that is odd. The one thing I have noticed with 8.0 on my 6p on fi is sometimes I lose data when I'm out and the phone loses wifi and switches back to lte. I have to reset the phone to get lte back.
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Just my 2 centers here for anyone else in this quagmire...
I had same issue. I've got a Nexus 6p on which I dirty flashed an 8.1 update of ABC Rom over an earlier 8.1 version of ABC Rom. After that, the issues began. At boot, I'd be on 3g and if I toggled airplane mode off and then on, I could get LTE for about 10 seconds. However, it would then drop back to 3g. I tried everything, as is stated above: revert to stock, older radio images, different SIM... nothing worked. I read about people manually configuring their APNs. However, I've got a Verizon SIM, so that option was gone.
Anyway, after reading this post, I got the idea that I might be able to mimic the solution without buying a Project Fi SIM that I don't want.
Here's what I did:
Open the Phone's Testing Settings by dialing: *#*#4636#*#*
Tap "Phone Information"
Scroll down and set the "VoLTE Provisioned" toggle to the "on" position.
Then, toggle airplane mode on and off.
Profit!
I'm not sure if this solution has any parallels to the solution that uses a project Fi SIM for a brief moment. However, I speculate that it may.
At any rate, I hope this helps someone else with this issue.
UPDATE:
It turns out this method is more of a work around at best. At first I noticed that I had to toggle airplane mode once after a reboot. That didn't seem too difficult. However, I then discovered that I could no longer make calls. Switching the VoLTE Provisioned toggle back off fixes the calling issue, but puts me back on 3G.
Uggg.
locolbd said:
I have a 5X on Project Fi and my 6P is on Verizon(the phone that is having problems).
As a last resort tonight I swapped SIM Cards and after a few minutes the Fi SIM in the 6P showed LTE service. (Maybe proof it was not the phone....??? who knows)
It took alot longer but my Verizon sim then showed LTE service on my 5X which is running Oreo btw. (Baffled at this point)
I placed the SIM cards back in their original phones and LTE is functional on both. On my 6P I enabled WIFI, downloaded data, toggled WIFI, rebooted, ran several speed test and the 6P still shows LTE and I haven't seen the dreadful roaming notification as of this message.
I guess problem solved. Now to install Magisk to get AP working.
Click to expand...
Click to collapse
Hey is ur 6p still running well with LTE? I did that with a att SIM card and my 6p read as a att SIM so I then put my Verizon Sim back in and it read Verizon LTE but then after like half an hour it changed back to roaming and 3g. I went to Verizon to get a new sim card but that didn't do any help at all. I would like ur feedback if possible. Thank you
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
j2t0621 said:
Thank you so much for posting this issue. My Nexus 6P was doing the same thing after 8.01 October security update. Tried everything, same as you listed. I found your post and recalled that during my initial setup I had to put my wife's Verizon SIM into the 6P due to the same issue occurring. I tried it again this time but it failed, issue persisted. So, based on your post, I got a Project Fi SIM for $30 (1 month) and just tried it again. Powered down, put in Fi SIM, power on, activated Fi (with new phone # for new line... will be cancelled if needed...), and got LTE without issues over Project Fi. Then, I did Network Settings reset, reboot, and powered back up. No issues with Fi.
So, to the point now. I put the Verizon SIM back in the 6P and BAM, full LTE, no issues. Whatever the non-Verizon SIM does to the phone internal settings I have no idea, but I can tell you that it was not a fluke that your process worked. The exact same thing worked for me.
Hope this helps anyone else with the same issue - you need to install a non-Verizon SIM, get LTE going, and then put the Verizon SIM back in.
Thanks again.
JT
Click to expand...
Click to collapse
Hey is the 6p still working well for you? LTE? I been following ur steps but I don't have project fi and I used my friends att SIM to kinda reset the network and I also reset the network too but it went back to 3g and roaming. Any help would be awesome. I don't want to have to get a new phone
Sent from my [device_name] using XDA-Developers Legacy app
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
j2t0621 said:
reply to divineazn716 (won't let me quote for some reason)
Hello. I have not had any issues with the 6P since posting this. I honestly can't explain why the method posted earlier works, there does not seem to be a visible change in the user accessible settings.... so i don't know if i can help you any further from a technical standpoint. I'm not sure why the Verizon SIM didn't fix it the 2nd time, in my case. Something to do with the internal calibration of the LTE antenna (i'm guessing).
If you're willing to go this far, a factory reset of the phone, then ATT SIM might be an option. I HAVE NO IDEA IF THIS WILL WORK, so take that advice with 'a grain of salt'. Something to consider if you don't mind resetting the phone but don't/can't get a Fi account.
I can say that it was worth the $30 to me for a Fi account since it fixed it, but maybe more importantly the knowledge that if it happens AGAIN I should be able to fix it.
I know that wasn't super helpful but that's been my experience since the post.
(unrelated, but since you're a 6P user you may find helpful, I had the dreaded early battery shut down and it got so bad it almost bricked my phone. I got a new battery by sending it to Huawei customer service and it works like a champ now. Better than when it was brand new, from a battery standpoint.)
Click to expand...
Click to collapse
Tea I bought a new battery on eBay for 10 and got it replaced and it's running awesome. Are you on a custom rom? Just wondering what else I can try to fix this. It's weird while on the att it worked fine with LTE. I'm thinking about getting a fi acct thought
Sent from my [device_name] using XDA-Developers Legacy app
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
k1ll3ry0 said:
I had this same exact issue... I'm on Verizon and I was running FireHound ROM, which I loved btw, but every time I restarted the phone/toggled airplane LTE would pop up for 30 seconds and I would be stuck on 3G. Huge bummer but I found this to be an issue on every current custom ROM. Defeated and abused I ended up returning to 100% stock, unrooted and locked bootloader, full LTE capabilities now. I did end up buying a new SIM which helped with some of the connectivity issues I was having before granted my original sim was cut twice and I had it for many many years. Try going 100% back to stock, replace your SIM(most places cost about $10) and you should be good to go. I can only chalk this up to be an issue with source provided to developers but I'm not sure where the discrepancy lies for DEVS that isn't consistent with a stock instal...
Tried all these ROMs:
FireHound
ABC
Resurrection Remix
DARK ROM
Cortex - Uneffected by the LTE issue but is a dead ROM as of now and is on a different vendor.
Click to expand...
Click to collapse
I will give this a try this evening
Sent from my [device_name] using XDA-Developers Legacy app
bleh im back to stock unrooted and locked and my signal is still crap. i guess i have to buy a new phone.... =*( i loved this 6P
Sorry to hear that. I'm just running stock android.