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.
Related
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.
so this is the second S7e and second SIM that I have been having this issue with. The phone will lose connection to the mobile network and the ONLY way to recover is to reboot phone. Reset Network Settings doesn't do anything. Toggle airplane mode doesn't do anything. Search for Network Operators doesn't do anything. I have a third phone on the way - but has anyone around here heard of or experienced similar? Am I missing something that I should be doing to correct this?
Thanks in advance
I too have this problem. Got a replacement refurbished phone under warranty and the phone has this problem
krishelnino said:
I too have this problem. Got a replacement refurbished phone under warranty and the phone has this problem
Click to expand...
Click to collapse
Did you pay the $20? I didnt want to pay the 20 so i sent the device to samsung. Should get it back friday or monday. The issue is definitely phone related. Im using a verizon s7 now and no issues like that arose. I even tried new sim.. My father is having same issue t-mobile s7 edge
Yes i had to pay 20. And it's disappointing I am having this issue with the replacement phone. I am having this problem on the U firmware as well.
Sent from my SM-G935U using Tapatalk
I've suffered the same issue from time-to-time and just do a restart....annoying as hell to be honest
Are you guys always in the same location when this is happening or is it just whenever and wherever? Or is it happening a one certain place where cell signal isn't that great? I had this same issue BUT only in my house so I had to get a network range extender from t-mobile to use at home.
This happens to me all the time. It's so annoying. At work, in the car, at home--it doesn't matter where I am. Have reset firmware multiple times and even rolled back once too. I think it has to do with the latest software because I never had this issue before the Fall/Winter. Hopefully Nougat fixes this!
Quickvic30 said:
Are you guys always in the same location when this is happening or is it just whenever and wherever? Or is it happening a one certain place where cell signal isn't that great? I had this same issue BUT only in my house so I had to get a network range extender from t-mobile to use at home.
Click to expand...
Click to collapse
I happens randomly in different places. For me i lose complete signal, and then only get back signal without data. I have to restart when this happens to get back data. Annoying as hell !
frappe33 said:
so this is the second S7e and second SIM that I have been having this issue with. The phone will lose connection to the mobile network and the ONLY way to recover is to reboot phone. Reset Network Settings doesn't do anything. Toggle airplane mode doesn't do anything. Search for Network Operators doesn't do anything. I have a third phone on the way - but has anyone around here heard of or experienced similar? Am I missing something that I should be doing to correct this?
Thanks in advance
Click to expand...
Click to collapse
I am having the same problem, this will be my 3rd phone 4th sim. I wish I knew how to fix it
I would try flashing different radios/modems, its worth a shot. Maybe try flashing the "U" firmware radios.
Nougat will fix it
My wife and I had the same issue on our tmobile s7 edge ... we got the 7.0 beta and now the issue is gone .... I bet it's radio and software related ... 7.0 will be out by the end of the month hope that helps...
I had this issue with my phone, and it was a huge pain. The biggest concern: I didn't know when my phone was off network (voice, data, etc.). The fix, for me, was simple: a new SIM card.
You may have an issue from a rejected permission on an app.
Had the same issue before but I did a hard reset and realised that I changed permissions on an app that wasn't written for 6.1.
ronstopable12 said:
My wife and I had the same issue on our tmobile s7 edge ... we got the 7.0 beta and now the issue is gone .... I bet it's radio and software related ... 7.0 will be out by the end of the month hope that helps...
Click to expand...
Click to collapse
I hope so! Been waiting for that before I try anything drastic, even though this issue is a huge pain in the ass. I'm glad others have come out of hiding to express their concerns with it as well. I thought I was the only one for the longest time having this issue.
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
jimfun said:
I had this issue with my phone, and it was a huge pain. The biggest concern: I didn't know when my phone was off network (voice, data, etc.). The fix, for me, was simple: a new SIM card.
Click to expand...
Click to collapse
Many of us have tried new SIM cards, but it's worth a shot if it's still not working consistently after Nougat is released.
---------- Post added at 02:22 PM ---------- Previous post was at 02:20 PM ----------
geeserver said:
You may have an issue from a rejected permission on an app.
Had the same issue before but I did a hard reset and realised that I changed permissions on an app that wasn't written for 6.1.
Click to expand...
Click to collapse
My and my friend's phones are both running pure 100% OEM Tmo stock without any apps disabled or touched at all and we have this issue and have done multiple resets. Pretty sure it's an actual hardware defect, or hopefully just a software one with the modem/radio.
krishelnino said:
Yes i had to pay 20. And it's disappointing I am having this issue with the replacement phone. I am having this problem on the U firmware as well.
Sent from my SM-G935U using Tapatalk
Click to expand...
Click to collapse
I was thinking about going that route. But I wasnt sure what condition the phone would be. How was you condition?
I sent mine to samsung and the things they replaced is the Coaxle cable "antenna" replaced 3 of them. I have been using the s7 from verizon on the U firmware so havent seen if it is fixed.
4ringsa6 said:
I was thinking about going that route. But I wasnt sure what condition the phone would be. How was you condition?
I sent mine to samsung and the things they replaced is the Coaxle cable "antenna" replaced 3 of them. I have been using the s7 from verizon on the U firmware so havent seen if it is fixed.
Click to expand...
Click to collapse
I received a refurb. Other than this problem, the phone is alright. I noticed this problem on receiving the phone it was running on T firmware. Then I switched to U firmware and radio but no difference. I called customer support yesterday, they said to go to a retail store to get the phone replaced. My worry is going through this process again and if I receive a bad device again what to do? After all refurb phones are like playing Russian roulette!
Sent from my SM-G935U using Tapatalk
I just had this start happening on mine... I really wish they would release nougat already. It is ridiculous they won't post an Odin flashable version of the release candidate if it does indeed fix the issue.
I also think its a specific tower configuration that is causing the issue that the radio can not understand. (Maybe 3xCA). Its happening in the same areas every time.
I just started having this problem in the past month. All at once I've been getting BT sometimes turning off, mobile networks failing to reconnect after I visit a no/low signal area (such as after a plane trip when the phone was in airplane mode). I've also seen wifi mode fight my attempts to turn it back on sometimes - toggling itself on and off a couple of times per second until I poke at enough settings to stop it. When BT turns itself off I have trouble turning it back on, sometimes it just goes back on, sometimes it refuses after a number of tries and if I wait an hour it goes back on just fine.
The folks at a BB Samsung kiosk said they could reflash it if I wanted to go that route, but that the nougat release would be out soon so it might be better to just wait for that. Has anyone had a Samsung rep re-image their phone to try to solve this?
flarbear said:
I just started having this problem in the past month. All at once I've been getting BT sometimes turning off, mobile networks failing to reconnect after I visit a no/low signal area (such as after a plane trip when the phone was in airplane mode). I've also seen wifi mode fight my attempts to turn it back on sometimes - toggling itself on and off a couple of times per second until I poke at enough settings to stop it. When BT turns itself off I have trouble turning it back on, sometimes it just goes back on, sometimes it refuses after a number of tries and if I wait an hour it goes back on just fine.
The folks at a BB Samsung kiosk said they could reflash it if I wanted to go that route, but that the nougat release would be out soon so it might be better to just wait for that. Has anyone had a Samsung rep re-image their phone to try to solve this?
Click to expand...
Click to collapse
If you were able to fix without a reboot you didn't have the same issue as this.
rocket31337 said:
If you were able to fix without a reboot you didn't have the same issue as this.
Click to expand...
Click to collapse
I guess I wasn't clear about that as I have several problems that are probably related, but behave a little differently.
BT dropping - can usually turn it back on, but sometimes it refuses. Usually don't need to reboot to fix this.
Wifi dropping - often have trouble turning it back on and have seen the widget toggle off and on repeatedly by itself. Sometimes have to reboot to fix that.
Mobile Network data (and voice sometimes) dropping - usually have to reboot. I think I may have recovered that once without a reboot, but the other few times it's happened in the past month since it started I have rebooted and that fixed it in all but one of the reboots - one time I rebooted and still had to fiddle with it a bit after the reboot before it came back. That may have been because I played too much with the network settings before the reboot and so had to undo that damage after the reboot. But, definitely rebooting is a fairly reliable step in fixing this problem.
All 3 started happening around the same time which is why I thought it was a software issue (I remember a small update a little over a month ago, but forget the details of it). It's nice to hear that others also have the mobile network problem, but if that is isolated in those cases then maybe I'm not seeing exactly the same problem. But, it is clear that rebooting is almost always required to get my mobile network data back so that again suggests that at least that part is the same as what this thread is discussing.
In looking at the T-Mobile updates page for the S7 Edge I see that the version I have (G935TUVU4APK1) was updated in early November - which tracks when I started having problems, and it includes a fix for "Domestic data roaming improvements", which definitely sounds like they may have played with the radios.
I am so ready for the Nougat update...
Android Oreo - "Mobile Data Has Run Out", but I still have lots of internet quota.
whenever you're on cell connection, and lost signal. when the signal got strong again, there's notification from mobile carrier "Mobile data has run out", "Tap to visit *operator* website"
you could fix this by activating and deactivating airplane mode. It's so annoying.
Does anyone experiencing this?
frnt said:
whenever you're on cell connection, and lost signal. when the signal got strong again, there's notification from mobile carrier "Mobile data has run out", "Tap to visit *operator* website"
you could fix this by activating and deactivating airplane mode. It's so annoying. Does anyone experiencing this?
Click to expand...
Click to collapse
Not ever. Which carrier/MVNO? Maybe it's time to get a new carrier/plan.
Yes, I've been having that message ever since the first boot after updating to Android O about three days ago. Toggling airplane mode on and off fixes the issue for about couple of hours. Battery also drains like crazy.
Now, today is the first time I'm out of the house away from wifi all day and I haven't get the message again. I'm back on wifi for about two hours now and all is well. Battery also seems to be back to normal. Hope it stays that way.
v12xke said:
Not ever. Which carrier/MVNO? Maybe it's time to get a new carrier/plan.
Click to expand...
Click to collapse
I'm on XL Axiata - Indonesia, this never happened before oreo.
Also this occurred on the second day after i installed oreo. :crying:
Rollies77 said:
Yes, I've been having that message ever since the first boot after updating to Android O about three days ago. Toggling airplane mode on and off fixes the issue for about couple of hours. Battery also drains like crazy.
Now, today is the first time I'm out of the house away from wifi all day and I haven't get the message again. I'm back on wifi for about two hours now and all is well. Battery also seems to be back to normal. Hope it stays that way.
Click to expand...
Click to collapse
Well, if the cell signal is strong that doesn't seem to happen. But if you're on weak signal where you could lose receptions, then that happened.
frnt said:
I'm on XL Axiata - Indonesia, this never happened before oreo.
Also this occurred on the second day after i installed oreo. :crying:
Click to expand...
Click to collapse
@Rollies77 Telkomsel, Pak! My driver used XL and always had problems. Don't know how you upgraded, but you could try downgrading your radio. Just fastboot flash the previous modem.img. (v3.81). Current version is 3.84. The radio is independent of the ROM version so it will work no problems. The older radio from Nougat may get your service back.
v12xke said:
@Rollies77 Telkomsel, Pak! My driver used XL and always had problems. Don't know how you upgraded, but you could try downgrading your radio. Just fastboot flash the previous modem.img. (v3.81). Current version is 3.84. The radio is independent of the ROM version so it will work no problems. The older radio from Nougat may get your service back.
Click to expand...
Click to collapse
Yup, XL Axiata. Just happened again. Gonna try downgrading the radio. Thanks.
Edit: No luck. Flashed 03.81 radio, reboot and greeted by "mobile data has run out" message.
I upgraded to stock OPR6 from Google's factory image. Clean flashed. Happened on first boot before rooted. But yeah probably XL is acting up.
Rollies77 said:
Yup, XL Axiata. Just happened again. Gonna try downgrading the radio. Thanks.
Edit: No luck. Flashed 03.81 radio, reboot and greeted by "mobile data has run out" message.
I upgraded to stock OPR6 from Google's factory image. Clean flashed. Happened on first boot before rooted. But yeah probably XL is acting up.
Click to expand...
Click to collapse
I'm on full stock, not rooted. So i don't think i can flash the radio.
So it's the XL's fault. I don't want to change my number, and i'm staying away from Telkomsel, their call center is the worst, also in my work place and home their signal is not very good.
Anyone not using XL experiencing this?
frnt said:
I'm on full stock, not rooted. So i don't think i can flash the radio. So it's the XL's fault. I don't want to change my number, and i'm staying away from Telkomsel, their call center is the worst, also in my work place and home their signal is not very good. Anyone not using XL experiencing this?
Click to expand...
Click to collapse
Correct, can't flash the modem partition with a locked bootloader. You could stop by any kiosk and pickup a simPATI and you'll quickly know the answer for very little money, but I tend to agree with you that XL is probably the culprit, and loading 8.0 was coincidental. I always had good service with Telkomsel, and was impressed by the service at their graPARIs, especially at Pondok Indah. There are also some settings to experiment with under Dev Options (don't have to be rooted). One is "Agressive Wi-Fi to mobile handover" and the other is "Mobile data always active". Toggle those and see what happens. Good luck. :good: @Rollies77
v12xke said:
Correct, can't flash the modem partition with a locked bootloader. You could stop by any kiosk and pickup a simPATI and you'll quickly know the answer for very little money, but I tend to agree with you that XL is probably the culprit, and loading 8.0 was coincidental. I always had good service with Telkomsel, and was impressed by the service at their graPARIs, especially at Pondok Indah. There are also some settings to experiment with under Dev Options (don't have to be rooted). One is "Agressive Wi-Fi to mobile handover" and the other is "Mobile data always active". Toggle those and see what happens. Good luck. :good: @Rollies77
Click to expand...
Click to collapse
Will try that on the Dev Options. Especially the "Mobile Data Always Active"
It's not graPARI's services that are bad, but their unified call center (147), My friends are experiencing bad service from call center (angry at customers, blaming customers for the problems even though the customer actually an IT guy), The product is Telkom Speedy, not their Mobile products. But they are still using the same 147 Call Center right?
google knows about this bug - have for a while, taking their sweet time to roll it out in the november security update.
I just upgraded to Oreo today (Project Fi 6p) and it completely cuts off my XL data in Bali.
Good job google.
There is a message at the end of this thread that suggests removing an app to fix it... I guess I'm going to give it a whirl.
https://productforums.google.com/forum/#!topic/phone-by-google/kw3ZcXd1BVs
---------- Post added at 11:09 AM ---------- Previous post was at 10:48 AM ----------
updating to say that the fix of using adb on an unrooted 6p to uninstall com.android.carrierdefaultapp got my data back. just uninstalled, and turned on airplane then off - and poof - LTE connection.
frnt said:
Will try that on the Dev Options...
Click to expand...
Click to collapse
Heads up
v12xke said:
Heads up
Click to expand...
Click to collapse
Not working
This did the trick!
netmasta10bt said:
google knows about this bug - have for a while, taking their sweet time to roll it out in the november security update.
I just upgraded to Oreo today (Project Fi 6p) and it completely cuts off my XL data in Bali.
Good job google.
There is a message at the end of this thread that suggests removing an app to fix it... I guess I'm going to give it a whirl.
https://productforums.google.com/forum/#!topic/phone-by-google/kw3ZcXd1BVs
---------- Post added at 11:09 AM ---------- Previous post was at 10:48 AM ----------
updating to say that the fix of using adb on an unrooted 6p to uninstall com.android.carrierdefaultapp got my data back. just uninstalled, and turned on airplane then off - and poof - LTE connection.
Click to expand...
Click to collapse
Works like a charm. although I'm rooted so I just uninstalled it using titanium back up. Thought Im gonna go back nougat. This saves me! :good:
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.