Related
Hey guys i have had some issues with my cell phone lately (hd2 tmous).
3-4 times a day i lose my signal completely and the only way to get it back is to restart the device. Sometimes my device even displays
I have tried using different radios as well no luck
that the simcard has been removed, i have tried everything
also it happens whether im at home, school or work, i live in an area that gets great reception so that should not be the problem.
messing with the band to keep it at gsm only
reverted back to auto
removed and replaced sim card
hard reset, new rom, stock rom, i always task29 before new rom as well
does this happen to anyone else, any ideas on what the problem may be?
A factory reset with formatting the memory is on the cards I think
johnerz said:
A factory reset with formatting the memory is on the cards I think
Click to expand...
Click to collapse
i just received a new sd card and it used to happen with my old formatted one, im not sure that would work? although it wouldnt hurt to see if it happens without the sd card in it.
It happens to me. Maybe a few times a week, though it will regain signal after a minute or few minutes. Sometimes I toggle the phone option off/on. Maybe that helps or maybe not. Rarely do I have to power down the phone, though I have done it a couple of time when I'm in a hurry.
It used to happen more often with the stock ROM from April of this year. Since I've upgraded a couple of times, it's gotten better. Hopefully the latest 3.14 ROM has fixed it some more.
have you complained to tmobile??? Maybe you need a new phone.
jfmckenna said:
Hey guys i have had some issues with my cell phone lately (hd2 tmous).
3-4 times a day i lose my signal completely and the only way to get it back is to restart the device.
does this happen to anyone else, any ideas on what the problem may be?
Click to expand...
Click to collapse
Browsing between topics of the H2 this one came to my attention.
I have exact the same issue! I also had it with my htc diamond. I moth ago when I received my HD2 (non branded) I thought it would be over. But no. it keeps losing signal. Freakingly annoying. I called tmobile (Netherlands sins i am from the Netherlands) and they would send me kindly enough a new sim.
But still…. The same issue.
I also did a hard reset, new ROM (cant go back to 1.33) and tried another phone. I gather it is a htc issue and some bad luck.
I didn’t had the error sim removed.
ok so i went about half a day with the sd card out and when i woke up this morning no signal again.
I gave t-mobile a call and explained to them what was going on. I was transferred to a pda/smartphone specialist, although i would say that any xda community member was more knowoledgeable than this rep. Anyway she asked me a couple of questions said there were no known issues and that i will receive a replacement phone and sim in 7 days and to return the old one phone. Hopefully with the new phone and sim i wont have this issue, im guessing they think its a hardware related problem. It bugs me that cheap crappy phones have no problem holding a signal and my top of the line hd2 does but lets hope had a faulty connection or something.
jfmckenna said:
ok so i went about half a day with the sd card out and when i woke up this morning no signal again.
.
Click to expand...
Click to collapse
Your problem (most likely) lies with a bad combination of Rom and Radio.
I know you have tried several radios, but you simply missed the compatible one.
http://forum.xda-developers.com/showthread.php?t=614119
see my posts in that thread.
apart from my provider having problems every now and then, I have not lost my connection again after flashing the right Radio.
reijkelhof said:
Your problem (most likely) lies with a bad combination of Rom and Radio.
I know you have tried several radios, but you simply missed the compatible one.
http://forum.xda-developers.com/showthread.php?t=614119
see my posts in that thread.
apart from my provider having problems every now and then, I have not lost my connection again after flashing the right Radio.
Click to expand...
Click to collapse
i have tried both the 2.13 stock rom radio and then the stock 3.14 combo both did not work.
resolved
received the new phone 3 days ago, so far have not lost service. It must have been a hardware issue with my phone. im using the same radio rom as the old phone except no signal loss, for anyone who is having the issue it may be worth calling tmobile to exchange your phone for a new/refurbished one.
Hi all,
Regular reader but hardly ever post!
I have a Galaxy S4 (GT-I9505) - with Android 4.4.2. Unrooted.
Purchased and used in Singapore on the Starhub network since around October 2013. Everything was working fine until approx Feb or March when the latest Android version, 4.4.2 got rolled out.
Ever since then I am experiencing regular disconnections from the network. But the phone does not re-connect back to the network again, the only fix is to restart the phone.
These disconnections are often once or twice a day, and are very frustrating because if I don't notice it, I may be off the network for hours before noticing it - and are therefore missing out on calls emails etc etc.
This only happened after the Android 4.4.2 got rolled out, so I am pretty confident this is the cause of the problem.
What I tried myself to fix:
- restore APN's back to default state
- Factory reset (both via settings, and via boot screen)
What I have been able to narrow down troubleshooting, is:
- Disconnects seem to only happen when Network Mode is "LTE/WCDMA/GSM (auto connect)"
- If I use network mode "WCDMA/GSM (auto connect)" the disconnections have not happened (yet!)
- When the disconnection does happen in the first mode, I cannot manually change the network mode. The radio buttons are greyed out, and if I try to select "WCDMA/GSM auto connect" the request times out (I forget the exact message - it does respond to the tap but then nothing happens)
So it seems to me this is some sort of software bug/fault introduced with Android 4.4.2 that affects 4G connections.
After that, I have taken it to Samsung for warranty service. I have now had 4 visits to them and they have not been able to fix it yet. This is what they have done so far:
- First visit - factory reset (despite telling them I already did that) - did not fix
- Second visit - checked hardware and replaced mainboard. Did not fix.
- Third visit - checked hardware again and factory reset again. Did not fix.
- Fourth visit - who knows. I think same as visit three but done via a Service Manager instead of staff, Did not fix.
When I first called them back in Feb or March, they said it was a "known Issue' and sugegsted to "wait for a patch". However since visiting them, they said the known issue was only with Note 3's (not with S4's) and replacing the mainboard on the Note 3's fixed the problem. In my case replacing the mainboard - twice - has not fixed it.
I'm getting very annoyed with Samsung who seem to just be trying the same thing each time and are not fixing it. Staying in 3G only mode is a workaround but not an acceptable solution.
Now they've asked me to take if back again - for a 5th time.
Beginning to wish I had never bought the S4, or at least never got Android 4.4.2.
So I thought I would turn to here for help instead, I think you guys and gals probably know more than the Samsung service staff!
Any suggestions?
By the way, I don't run any memory/battery saver apps. I do run one data usage monitoring app that I thought perhaps was conflicting, so I tried not installing it after one of the resets, but the problem continued.
Chikara71 said:
Any suggestions?
Click to expand...
Click to collapse
you CAN try other modem flash, but be careful with your warranty.
I do not know about the warranty conditions in your country, but in EU normally 3 unsuccessful repairs = phone refund or replacement.
I would try reflashing stock file or just flash a different modem
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Dial *#1234# and paste here what appears.
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUFNBE
CP: I9505XXUFNBE
CSC: I9505OLBFNB3
I should add, I took it in *again* to Samsung, to the Service Manager. Said they would replace the antenna and try that, which they did.
Still have the same problem though.
Not sure who to believe, Samsung are starting to run out of ideas and starting to say it may be a network issue. But if the network is down, then the phone should automatically reconnect once the network is back available again. And it doesn't.
I'm convinced it's a bug introduced with KitKat, as the problem only started then, but of course I cannot prove it...
felgrab said:
Hello, just like you i have been reading the post but never posting because i just came here to learn, nothing to share from this side...sorry.
But i am having the same problem as you. I bought my phone in Switzerland on march 2013 but i live in Uruguay. I was just thrilled with my s4 until the 4.4.2 update came out. My connection keeps on crashing and it doesnt matter if its on 4g or 3g just make me miserable all day. Only the two of us is having this type of problem??
I believe is some kind of issue with the new bootloader i just updated with a patched rom that came for Germany last week (the one with kids mode) the phone work fine for a hours and then crashes, so this update didnt work. I have also flashed very differents official roms and modems but nothin seem to affect the problem.
I have another problem even though my s4 is 4g i cant connect to 4g network, every configuration is fine i just cant connect, any thougths??
Thank you very much.
Sorry for my english.
Click to expand...
Click to collapse
Sounds very similar to my problem, that it just started with Kitkat only. I'm sure it can't be just us two having this problem! I don't have anything special or different installed on my phone, and it's too suspicious that it was working fine, 100% perfectly until the KitKat software came out...
Joku1981 said:
Dial *#1234# and paste here what appears.
Click to expand...
Click to collapse
AP: I9505XXUGNE5
CP: I9505XXUGNE5
CSC: I9505OXAGNE5
Thank you so much for giving us a hand!!
Chikara71:
I know it just cant be the two of us from such diferent places in the world but, i just cant find any similar in any post or google. It has been almost 3 months from the update an me using another phone...
Well I thought I would post again to close the loop.
After Samsung tried 5 times to fix my phone, checking hardware and trying to reinstall the OS with no luck, they suggested I try replacing my SIM card.
Surprise surprise, it has fixed the problem with no recurrence yet after a week so far.
I still don't understand how the sim card could be the problem, especially as my phone was working perfectly right up to the Kitkat software update. All I can assume is somehow KitKat either had an incompatibility with my simcard (maybe the new sim is technically slightly different?) or maybe KitKat somehow changed something on the simcard, if that's even possible.
Interestingly, I did contact my telco first, and they told me to contact Samsung. As it turned out, the fix was in the control of the telcom right from day one.
Anyway, so far the problem is resolved, so I thought I would post this here to help anyone that may have this problem.
Phone is stock and not rooted.
This is extremely strange. I'm on Vodafone in the UK and I had installed the 7.0.1 update a few days ago. All was running fine.
Anyway, the Play Store issue had me confused, so instead of uninstalling updates, I decided to hard reset.
Did that and from that moment on the Sim card seems to have gone into a fit of turning itself off and on every 1-2 seconds.
I have reset a number of times and have now installed the 7.1.1 update, along with a hard reset and nothing has changed.
I have tried an EE Sim in the phone and this works fine. My voda sim I put in a Galaxy S 7 and that seemed fine too.
Yet when it is put back into my phone, it goes mad.
I only run one sim and have tried with SD Card in/out.
I am tempted to call it a faulty sim and go and get a new one, but thought I'd check here first.
Any experiences or ideas?
TIA
The plot thickens...a bit.
When I insert 2 vodafone sims, it works fine. Both sims are stable and I can make/receive calls as per normal.
As soon as I remove the one of the sims, it carries on as per usual constantly activating and deactivating sim.
Some more info...
Upon a hard reset the sim is stable and I can see data connection. I follow through the initial startup screen and skip as much as I can skip. Again, remains stable.
The last screen I get to is IZ location or something (can't remember) and asks whether you want to enable for h/w acceleration. I have tried this both on and off.
As soon as you click finish and it goes to the home screen for the first time, the sim immediately begins to fluctuate showing both signal bars empty, then one, then one with signal, then repeat.
Viewing from the dual sim settings page, you can see the sim activate, say it's vodafone, the disable as if it had been removed.
About as strange as it gets!!
Right, resolution in the hope that it helps someone else
After trying every conceivable way to sort this, it was time to downgrade.
Went back to B10 package from the German site:
http://www.ztemobile.de/support/downloads/?product_id=2100
Will install everything and upgrade to Nougat again...possibly!
Yep, just been through the exact same thing. I had to go back to b10, whatever you do don't factory reset in-between updates back to 7.1.1.
Don't do anything in fact, just upgrade.
I ended up losing my great battery life because of this, I wish I'd left alone.
Good luck.
Mike
Make sure you have OEM unlocking disabled in developer options. It was required to be on for the original sideoaded B10.
Sent from my ZTE A2017G using Tapatalk
Ranny99 said:
Make sure you have OEM unlocking disabled in developer options. It was required to be on for the original sideoaded B10.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
I was trying to look for discrepancies between the B10 6.0.1 and the 7.0.1 but there were too many.
I'm quite tentative about moving off MM to nougat after the shenanigans the other day.
I had a similar problem when I made the first upgrade to 7.0.
My primary (French Prixtel) SIM would turn on/off constantly - and was basically unusable... however a UK EE Sim was fine - when either run alone or in the 2nd SIM slot.
I tried my wife's Prixtel SIM in the A7 - it was fine ... tried my SIM in the wife's Honor 8 ... and it was fine ....!!
I tried downgrading back to MM B10 - my SIM still didn't work anymore - back to 7.0 .. the same.
Finally I reported my SIM to Prixtel as non-working - and they replaced it FoC ... and the new one works fine.... also after the recent upgrade to 7.1.1.
Looloup said:
I had a similar problem when I made the first upgrade to 7.0.
My primary (French Prixtel) SIM would turn on/off constantly - and was basically unusable... however a UK EE Sim was fine - when either run alone or in the 2nd SIM slot.
I tried my wife's Prixtel SIM in the A7 - it was fine ... tried my SIM in the wife's Honor 8 ... and it was fine ....!!
I tried downgrading back to MM B10 - my SIM still didn't work anymore - back to 7.0 .. the same.
Finally I reported my SIM to Prixtel as non-working - and they replaced it FoC ... and the new one works fine.... also after the recent upgrade to 7.1.1.
Click to expand...
Click to collapse
I tried multiple vodafone sims and had the same problem. Like you both Voda sims worked fine in other phones.
I would have gone the local Voda store, but they were...let's say 'challenging' to say the very least!
Good to know that other providers are affected too
You have this problem because you most likely have unlocked your bootloader. ZTE know about this problem, the only way to solve this is to go back to marshmallow, lock your bootloader then go back to the nougat build.
I've tried everything to get my phone to get network working again. I've re-flashed old and newer images, got a new sim, messed with the APN settings and I just can't get it to work since yesterday.
When it started, my phone was sitting on charge. It was working just fine before I had put it down for 30 minutes. Upon checking for any messages I saw it wasn't getting any service so I restarted the device and was greeted with the 7.1.2 july update installer. Waited for it to finish and once fully back onto the home screen for a few minutes service still never came back. Turned it off and on a few times and turned airplane mode on and off few times still never came back. Turned it off for the night till today when I started playing with it more, factory reset, flashed 6.0, 7.1.2 june, 7.1.2 july, O beta 3 and none of it was getting the network to work.
Went and got a new sim, guy at the store also tried a floor sim and none of them were working but both my old and new sim do work just fine in a backup phone. The 6P reads there is a sim in and it knows its AT&T, but it won't pick up signal at all.
Any help with this? There really isn't much on this topic, but I do see a sim card no installed issue which my phone knows there is a sim card in it.
that happened to a nexus 6p i bought from a guy off craigslist. at first it worked with tmobile and metro pcs then after a few weeks it stopped working but i had switched to cricket anyway and it worked on cricket but not on tmobile or metro, so then i checked imei and it was black listed,.... being that it was a BYOD it wasnt bound to any network so i was like why would it be blacklisted... didnt make sense but i stayed with cricket and to this day it works..
i42o said:
that happened to a nexus 6p i bought from a guy off craigslist. at first it worked with tmobile and metro pcs then after a few weeks it stopped working but i had switched to cricket anyway and it worked on cricket but not on tmobile or metro, so then i checked imei and it was black listed,.... being that it was a BYOD it wasnt bound to any network so i was like why would it be blacklisted... didnt make sense but i stayed with cricket and to this day it works..
Click to expand...
Click to collapse
I just checked to see if it was blacklisted and its good. Google & Huawei won't service it due to it being out of warranty so rn its pretty much a dead phone for me. Is there is any tests I can run to see if the network radios are working or even turned on?
I had this exact same problem a few months ago with my other 6P. Thankfully it was right before my warranty ran out so i was able to get a replacement, but as far as I know, there isn't much you can do with it network wise.
@MadBullBunny could it maybe be the antenna inside? If you've tried other carrier Sims and flashed different radios what else I wonder. Since it's not working maybe worth a peak if your comfortable opening her up.
Exodusche said:
@MadBullBunny could it maybe be the antenna inside? If you've tried other carrier Sims and flashed different radios what else I wonder. Since it's not working maybe worth a peak if your comfortable opening her up.
Click to expand...
Click to collapse
I really didn't want to go that far and I rather just dump it on craigslist for $250 if its just an issue with at&t. is there some sort of test to see if the antennas are working?
have you try resetting your network settings? this has happen to me right after a update and resetting the network settings fixed it for me. i'm on project fi.
boxcar8028 said:
have you try resetting your network settings? this has happen to me right after a update and resetting the network settings fixed it for me. i'm on project fi.
Click to expand...
Click to collapse
Dude... Not trying to be rude, but really?
Anyway I've been waiting for a response back from google. Huawei pretty much told me tough luck since I didn't have warranty left on it. Told google that I was pretty much shoved out by them and argued that a phone not even 2 years old can't get serviced by a multi billion dollar company is pretty embarrassing. Supposedly its being routed up but I was told that a couple days ago when it was going to take 24-48 hours to get back. Right now I'm trying last ditch effort to drain the battery completely and stick it in some rice to possibly suck any possible moisture out that maybe my butt sweat caused. If this doesn't work I'm going to go to other service's stores and ask to try their sims in the phone out.
Fun tip: My phone is been running in boot mode for almost an hour after it turning off from android os for battery being dead. I've been doing random stuff in boot mode trying to make it die completely and it doesn't want too.
So being back and fourth with google for almost a week I was pretty much told tough luck buddy. It fathoms me that a company who created the android OS doesn't even have a service center or require its manufacturers to provide a service center for phones that aren't even more than 2 years old.
My nexus 6p is posted on craigslist and I've bought myself a s8+. so word of warning to you all who buy any google product or from them, just don't. If you have any issues you'll just get a run around. I've had to tell my issue to google at least 20 times and they still didn't care and kept trying to push me to hauwei when neither of them wanted to help.
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.