Related
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.
Edit 5: Gonna go ahead and declared this solved, the problem hasn't come back since I factory reset and reflashed MHC19I (not Q) from scratch. No more issues with wifi not autoconnecting or taking excessively long to connect, no more battery drain (got nearly 48 hours this weekend including a good amount of time spent in a poor/oversaturated service area at the Grand Prix), etc. Probably going to wait until the May update before flashing any OTAs.
Edit 4: Two days later and still seems to be working fine. I'm seeing some other issues on the April update (significant battery drain, slow wifi connect, etc.), so this morning I tried rolling back first to January (wouldn't get LTE) and now to March (fine so far). With the exception of keeping my media, I'm setting this up completely new, i.e. redownloading everything from the Play Store, to avoid any weirdness from restoring backups.
Edit 3: A factory reset done via TWRP (which retained my media) seems to have solved it for now. At any rate it's been acting normal longer than anything I've done before. This includes restoring my apps + their data via TitaniumBackup (but not system backups), reflashing SuperSU and otherwise getting my phone back to where it started. I've tested things that were known to cause it before like having wifi active but leaving my signal area and having it revert to cell data. The only issue I've noticed now is that wifi no longer seems to autoconnect when it's in range of my router. Not a huge deal but kind of annoying, if anyone has a fix for this I'd appreciate that too.
Edit 2: This issue is NOT resolved. The problem came back after working for a little while. Once the LTE fails the wifi will never reconnect on its own. It seems like everything still works except loading images from anything (reddit, instagram, etc.) and loading bookmarks. I can make google searches, download apps, go into reddit comments, go to instagram profiles I've never been to before, and so on. Is my device defective?
Edit: It appears that going through the motions of flashing the latest update (save for recovery.img and formatting userdata) has fixed the issue. This includes reverting to the stock kernel and flashing the vendor.img, which I hadn't done before. Wifi can be flipped off and on and will reconnect and there are no "!"s anywhere in sight. Strange considering I essentially went through the whole process minus the stock kernel and vendor.img, just out of order, with no effect.
Can anyone offer insight as to what piece of that process might have fixed this? It's not clear to me which pieces of the update are responsible for wifi and cellular connectivity besides the radio and kernel. Leaving the original post below in case anyone has anything to add or is going through this same issue. I'll update this post if the issue returns.
---
As of just this afternoon I'm suddenly getting a strange new issue that I can reproduce pretty consistently. I first noticed that my wifi signal was claiming to be connected but with no internet, and showed a little exclamation point next to it. I disabled wifi, and noticed the exclamation point jumped over to LTE. In both cases, I can still essentially use the connection. I disabled cellular data with wifi connected and could still browse the web, and likewise if I disabled wifi and the exclamation point was back on the LTE symbol. However, I notice some apps like Instagram will refresh posts but no longer load images, and reddit will load posts but not follow any links or load any images either.
Things I've tried:
-Flashed the 2.50 radio (down from 3.61)
-Flashed the MHC19Q system.img and cache.img
-Installed ElementalX kernel (at first it looked like it fixed the LTE issues, but really it just made the "!" go away; still seeing the same issues when I connect to wifi and then disconnect)
-Deleted and readded the nxtgenphone APN (I'm on AT&T)
-Tried to get into *#*#4636*#*#; I get "Connection problem or invalid MMI code."
-Cleared cache/dalvik in recovery (hey, you never know)
-Rebooted my router to make sure it's not an issue there; all other wireless devices on my router are fine
-Removed and reseated the SIM card
In all cases I can still send and receive texts and certain apps will continue to function about halfway, such as Instagram mentioned above. Switching airplane mode on and off doesn't help. Furthermore, once the wifi connection first gets the "!", it will no longer automatically reconnect as it doesn't find a working internet connection.
After an initial reboot it will appear to be fine; wifi connects automatically, no "!"s anywhere in sight, and everything seems to work. As soon as I disconnect from wifi, this issue starts. As mentioned, it will no longer reconnect to wifi and cellular data doesn't seem to work.
Anyone have any thoughts or suggestions as to what the issue may be? This started out of the blue this afternoon, I haven't made any changes to my phone since flashing the April image. My bootloader is unlocked and I'm rooted, and save for the ElementalX experiment (going to go back to the stock kernel) everything else is stock.
Any help is appreciated. If you need any more info, let me know.
Did your problem get resolved or did it come back. I'm having a number of problems on t-mobile since upgradingj to mhc19q
acathrow said:
Did your problem get resolved or did it come back. I'm having a number of problems on t-mobile since upgradingj to mhc19q
Click to expand...
Click to collapse
So far so good, the issue hasn't returned, although I'm really not liking the latest update. I'm considering rolling back (is that something I can do? I don't see why I couldn't) to January or so.
I'm still in limbo. T-mobile have been helpful but it's in Google Nexus support's hands and they have been less than responsive to say the least.
Next step is likely replacement device but in the mean time I just finished flashing 19i and will see if that has the same issues, then I'll try the previous build.
I'm kicking myself that I didn't check the version numbers I was on before applying April update. Ah well, lesson learned,
acathrow said:
I'm still in limbo. T-mobile have been helpful but it's in Google Nexus support's hands and they have been less than responsive to say the least.
Next step is likely replacement device but in the mean time I just finished flashing 19i and will see if that has the same issues, then I'll try the previous build.
I'm kicking myself that I didn't check the version numbers I was on before applying April update. Ah well, lesson learned,
Click to expand...
Click to collapse
Out of curiosity are you doing a full wipe before flashing different builds? I noticed in my case the issue didn't go away until I did a factory reset, which I think suggests something was corrupt or otherwise affected in the system partition. Since doing a factory reset (and now after doing a couple more) the issue seems to have gone away and I'm no longer having wifi/LTE issues - well, except for not getting LTE at all on the January update, so now I'm back on MHC19i.
Current status: My issue appears to be with t-mobile band 12, the new band that t-mobile is rolling out now.
It appears that the phone "prefers" band 12 to the older bands (like 4).
Rolling back to an image before band 12 was added (eg MDB08K from October) gives me back reliable LTE on band 4.
Sent logs to t-mobile and Google and waiting.
Sometimes I'll lose signal only to have it reconnect immediately.
Here's a screen recording of it: https://youtu.be/v9skns6qntE
It all started last October 2016. My 6p is stock, rooted and I have been with Project Fi for over a year now without any issues until last Oct 2016. Out of the blue I loss my cell signal but only with T-mobile but not Sprint, nothing will bring it back until I reboot my 6P I can’t even make or receive a phone call and google Fi customer services was no help.
I updated to 7.1.1 in December’s update and all cleared up. I stop having my cell signal stopped dropping or when it does it would pick up the signal immediately, all seems good to go but, until yesterday. I loss my cell signal but this time it didn’t come back I had to reboot.
I have done some Mods with Google assistant and not much else, so I have no idea what my be causing this, hopefully Feb’s update will help.
boxcar8028 said:
It all started last October 2016. My 6p is stock, rooted and I have been with Project Fi for over a year now without any issues until last Oct 2016. Out of the blue I loss my cell signal but only with T-mobile but not Sprint, nothing will bring it back until I reboot my 6P I can’t even make or receive a phone call and google Fi customer services was no help.
I updated to 7.1.1 in December’s update and all cleared up. I stop having my cell signal stopped dropping or when it does it would pick up the signal immediately, all seems good to go but, until yesterday. I loss my cell signal but this time it didn’t come back I had to reboot.
I have done some Mods with Google assistant and not much else, so I have no idea what my be causing this, hopefully Feb’s update will help.
Click to expand...
Click to collapse
I really hope this is fixed by the February update.
Yea its Radio related (duh huh lol). I flashed the newest radio from Jan and same crap. The ONLY radio that works consistent and NEVER loses signal is the 03.61.
alex__usa2002 said:
I really hope this is fixed by the February update.
Click to expand...
Click to collapse
Does it change bands (or carriers) when coming back up? I don't use Project Fi (AT&T) but sometimes the phone switches bands when a stronger signal is available. Have you tried the LTE Discovery app? It shows not only the band and signal strength you are connected to, but all neighbor cells and their strength. You can also quickly reset the connection to grab the strongest cell tower. Might give you some additional information. I guess you've already tried the 03.79 radio from N4F26J, rather than 03.78 on N4F26I. You may also see whether or not you can duplicate the problem on a different (non-Fi) SIM.
v12xke said:
Does it change bands (or carriers) when coming back up? I don't use Project Fi (AT&T) but sometimes the phone switches bands when a stronger signal is available. Have you tried the LTE Discovery app? It shows not only the band and signal strength you are connected to, but all neighbor cells and their strength. You can also quickly reset the connection to grab the strongest cell tower. Might give you some additional information. I guess you've already tried the 03.79 radio from N4F26J, rather than 03.78 on N4F26I. You may also see whether or not you can duplicate the problem on a different (non-Fi) SIM.
Click to expand...
Click to collapse
I'm on Metro PCS which uses T-Mobile towers. I've tried everything already, I'm on my second 6p. I RMA'd the first one for this same reason. I've tried a new sim card. The only thing that works is using radio 2.50. Some people are saying radio 3.61 and 3.72 works. I've experienced drops with those radios although not as frequent. I suggest anyone with this issue report it here: https://code.google.com/p/android/issues/detail?id=232089
boxcar8028 said:
It all started last October 2016. My 6p is stock, rooted and I have been with Project Fi for over a year now without any issues until last Oct 2016. Out of the blue I loss my cell signal but only with T-mobile but not Sprint, nothing will bring it back until I reboot my 6P I can’t even make or receive a phone call and google Fi customer services was no help.
I updated to 7.1.1 in December’s update and all cleared up. I stop having my cell signal stopped dropping or when it does it would pick up the signal immediately, all seems good to go but, until yesterday. I loss my cell signal but this time it didn’t come back I had to reboot.
I have done some Mods with Google assistant and not much else, so I have no idea what my be causing this, hopefully Feb’s update will help.
Click to expand...
Click to collapse
Yup mine does that, while walking around trying to catch pokemon, I'll get No Network. It'll come back after about 15-20 seconds. Happens often in Downtown San Diego. I usually just switch from Tmobile to Sprint when that happens. Though Sprint service is weaker...
When it happens, I notice on the Signal Info app that TMobile is jumping around between LTE, HSPA, HSDPA. 2G Edge, all within a few minutes.
I am on latest factory stock image.
d08speed3 said:
Yea its Radio related (duh huh lol). I flashed the newest radio from Jan and same crap. The ONLY radio that works consistent and NEVER loses signal is the 03.61.
Click to expand...
Click to collapse
Where did you find 03.61 and is that specific to MM, LP, or nougat?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 03:45 AM ---------- Previous post was at 03:43 AM ----------
Happens to me too...I had the same issue with the last phone I had (HTC M8), but that was a common CM bug at the time. I'm on 03.79 radio....vendor,BL, and radio are all up to date.
Sent from my Nexus 6P using Tapatalk
Same problem with my Nexus 6P on Verizon. Cellular signal is lost and only restored by rebooting the phone. Happens 1-2 times daily. I'm on Android 7.0 build NBD91V.
So I had an interesting experience with the same thing. Was running a custom rom that is very close to stock and updated to the most recent security update. Shortly thereafter, my carrier connection would drop (didn't notice at first because if I was connected to WiFi, it would be hard to tell). Only a reboot of the phone would fix it, for often no more than an hour or 2. So I started by wiping the device. Then I went to a different custom rom. And then finally, I went back to stock using "flash-all.bat" from the factory image. But alas, the issue continued. The last thing I did, which seems to have resolved it so far (12+ hours without a disconnection), was to relock my bootloader. Just in case it helps someone else. Is it possible that the new radio + an unlocked bootloader is causing the issue?
I am it's so annoying! I've used so many Roms and it happens anyways. I've updated the radio and bootloader and still doesn't help. I'm on T-Mobile as well
bgboii said:
I am it's so annoying! I've used so many Roms and it happens anyways. I've updated the radio and bootloader and still doesn't help. I'm on T-Mobile as well
Click to expand...
Click to collapse
for me it's T-Mobile's band 12 that's dropping my single. please see my Post....
https://forum.xda-developers.com/nexus-6p/help/project-fi-t-mobile-band-12-t3546303
boxcar8028 said:
for me it's T-Mobile's band 12 that's dropping my single. please see my Post....
https://forum.xda-developers.com/nexus-6p/help/project-fi-t-mobile-band-12-t3546303
Click to expand...
Click to collapse
For me it's band 4 I think.
So I have a Huawei p8 gra-L09 with Huawei P8 [ROM][6.0] fRomFuture - Home that I installed a couple of months ago. Everything has worked perfectly up until recently when my phone does not find any 3g networks, only 4g. When I try to make a call it's stuck on 4g. I don't even know if my phone is the problem or if it's my carrier. I tried to call them, they said they "made the network better".... But the problem came back after 1-3 days again.
Can I solve this somehow? My phone is also rooted but that doesn't really matter I guess..
Check the fRomFuture thread, another guy in that thread has the same issue..
did you managed to get the issue resolved?
Well, nope. Turning of 4g sort of fixes the problem I think. The connection drops sometimes but most of the time it works. Also I changed to stock b392 because I could not turn off 4g in the build that was used in fromfuture - home for some reason. It automatically turned it on just after chabging to only 3g/2g.
Still doesn't work as intended though and I am 99.9% sure it is not because I don't know how to flash. Used adb and fastboot and unlocked bootloaders and whatever on so many phones since my first smartphone (htc wildfire).
Are you by any chance Swedish or scandinavian? Could it be that it is not compatible with the networks in some countries or something?
melonsmasher100 said:
Well, nope. Turning of 4g sort of fixes the problem I think. The connection drops sometimes but most of the time it works. Also I changed to stock b392 because I could not turn off 4g in the build that was used in fromfuture - home for some reason. It automatically turned it on just after chabging to only 3g/2g.
Still doesn't work as intended though and I am 99.9% sure it is not because I don't know how to flash. Used adb and fastboot and unlocked bootloaders and whatever on so many phones since my first smartphone (htc wildfire).
Are you by any chance Swedish or scandinavian? Could it be that it is not compatible with the networks in some countries or something?
Click to expand...
Click to collapse
No i am in UK; i bleive the single sim version supports all the bands, at least here in UK; it is a phone i just bought off ebay and i can return it but I wanted to be sure it wasn't something that could not easily be fixed before doing so.
Hi again. I have sort of figured something more out about the problem. This morning 3G did not want to work again. So I googled, and googled and googled. Tried everything basically. Then I noticed that my APN settings are not what they were last time I set them(???). So I went into my carriers website. Set the correct apn values and removed any unnecessary values that did not seem to affect anything. Then it immediately worked again. Now I have no idea how phones sets the default settings but it seems like they are wrong? Maybe this was just random that it started working after applying the correct settings again. No idea, going to see if it works all day or if it randomly stops working as earlier.
Edit: 5 hours later still works and the connection hasnt stopped randomly.
Ok so it has worked for 13 hours. It's actually weird if the APN settings for 4g broke the 3g connection sometimes randomly throughout the day, right? I don't know how apn settings really work but I remember setting a port number and also changed the name of the APN so that I can be sure it does not change to something else.
ugh, I give up. Now it stopped working again since yesterday. It feels like it's my carrier but so many people have this problem so I guess it's something else..
Nevermind I don't give up. I found a solution . When 3g/calls stop working the phone usually gets really, really hot. So putting it in the freezer for a couple of minutes actually fixes the problem for me, atleast until the phone gets really hot again. I have tried it four times now and every time it has worked.
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.