Related
Hello all, my family all just got new phones. Both my mom and dad got the S4. I activated my dad's phone with no problems and everything is running great. It did not get the OTA update so it is still on 4.2.2. My mom's phone on the other hand has some issues. Right after activating and running initial stuff, I got the OTA update message, and decided to update that phone. it downloaded, rebooted, installed, and rebooted again. It seemed everything went fine.
Upon further setting up her phone, I noticed that there would be a notification about Sprint ID downloading a "Default ID" pack, and it trying to install it. But it would fail every time. Any changes to the internet connection (going from 3g to wifi or vice versa) would trigger Sprint ID to start up over again and download and fail to install. This kind of gets annoying after a while. Since my mom's phone is not rooted, I can not freeze or uninstall the Sprint ID apk. Force closing it does not help, because it starts up again when changing internet. I spent a good 30 minutes with the Sprint Chat online with no help. Even factory resetting does not fix the problem. Sprint could not help, and forwarded me to a Samsung chat person online. After 20 minutes with that person, they said that they went through all troubleshooting steps and could not help and asked me to call their hotline (which is open on Monday).
The odd thing is, according to Sprint's website, Sprint ID isn't supported on the S4, and my dad's S4 with 4.2.2 does not have it. could the 4.3 update have accidentally added Sprint ID? Is there any way to remove Sprint ID without root? Or root with 4.3, and somehow flash back to stock 4.2.2 without messing with knox? I can try going to the Sprint store tomorrow and see if they can do anything, but I would rather try alternatives first.
on the phone that's already taken the 4.3 update you cannot go back to stock 4.2.
You can however root. Then install titanium and freeze the 'sprint installer' and sprint id applications.
Just wait 'till tomorrow do not take any risks because it's your mother's phone and she wont need root. Service will flash a rom to it hope it will fix it. Have a good day
Sent from my E-Tab10 using xda app-developers app
Yes, take it to Sprint and have them fix it. You did nothing wrong so it shouldn't be upu problem.
Sent from my SPH-L720 using Tapatalk
So I went to the Sprint store today, to see if I can get my mom's phone fixed. According to the technician, there is nothing they can do until Sprint pushes an update to fix this problem. The technician tried fixing a previous customers phone with the same problem, and came to this conclusion. He even said switching out the phone wont help because eventually the 4.3 update will push to that one and might glitch like this phone. I guess I will hold back on updating my dad's phone when he gets his OTA.
I have temporarily fixed the notification by turning off notifications for Sprint ID, so it wont keep on popping up, but I do not know if it will try to download in the background or not.
I heard Sprint was going to push an update to fix the Knox notification showing up when switching to wifi on the S4 and Note 3, and hope they might attach a fix to this in the update.
chaosacolyte said:
So I went to the Sprint store today, to see if I can get my mom's phone fixed. According to the technician, there is nothing they can do until Sprint pushes an update to fix this problem. The technician tried fixing a previous customers phone with the same problem, and came to this conclusion. He even said switching out the phone wont help because eventually the 4.3 update will push to that one and might glitch like this phone. I guess I will hold back on updating my dad's phone when he gets his OTA.
I have temporarily fixed the notification by turning off notifications for Sprint ID, so it wont keep on popping up, but I do not know if it will try to download in the background or not.
I heard Sprint was going to push an update to fix the Knox notification showing up when switching to wifi on the S4 and Note 3, and hope they might attach a fix to this in the update.
Click to expand...
Click to collapse
Thanks for the update! the auto install of the Sprint ID on my gf phone was driving me crazy..
chaosacolyte said:
Hello all, my family all just got new phones. Both my mom and dad got the S4. I activated my dad's phone with no problems and everything is running great. It did not get the OTA update so it is still on 4.2.2. My mom's phone on the other hand has some issues. Right after activating and running initial stuff, I got the OTA update message, and decided to update that phone. it downloaded, rebooted, installed, and rebooted again. It seemed everything went fine.
Upon further setting up her phone, I noticed that there would be a notification about Sprint ID downloading a "Default ID" pack, and it trying to install it. But it would fail every time. Any changes to the internet connection (going from 3g to wifi or vice versa) would trigger Sprint ID to start up over again and download and fail to install. This kind of gets annoying after a while. Since my mom's phone is not rooted, I can not freeze or uninstall the Sprint ID apk. Force closing it does not help, because it starts up again when changing internet. I spent a good 30 minutes with the Sprint Chat online with no help. Even factory resetting does not fix the problem. Sprint could not help, and forwarded me to a Samsung chat person online. After 20 minutes with that person, they said that they went through all troubleshooting steps and could not help and asked me to call their hotline (which is open on Monday).
The odd thing is, according to Sprint's website, Sprint ID isn't supported on the S4, and my dad's S4 with 4.2.2 does not have it. could the 4.3 update have accidentally added Sprint ID? Is there any way to remove Sprint ID without root? Or root with 4.3, and somehow flash back to stock 4.2.2 without messing with knox? I can try going to the Sprint store tomorrow and see if they can do anything, but I would rather try alternatives first.
Click to expand...
Click to collapse
I just received a replacement phone that is having the same issue, and it's on 4.2.2 - has not received ota update notice. In addition, the CF Root Procedure which seems to work for most everyone is not rooting my phone.
Wi-Fi Calling is not working at all on my stock s7. Is anyone else experiencing this? Getting enablement error. Spoke with sprint tech support who is stumped and now escalating up to higher level team.
Rest of phone (including wifi and hotspot/tethering) working as it should.
Saw one post about disabling Bluetooth and BT share. tried that with no improvement.
-Josh
What kind of testing would help?
I have never used this before, so keep it simple, lol
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
cwb1231 said:
I have the same problem. . They told me, after escalating, that it was am account code error. . I am trying now to enable. . Update it works now after whatever account coding they updated
Click to expand...
Click to collapse
That sounds promising.They have called me three times to keep escalating. Any chance you would PM me your #. I can ask them to look at your acct to figure out how to fix mine.
Also if you have air rave try turning that off
cwb1231 said:
Also if you have air rave try turning that off
Click to expand...
Click to collapse
I didn't have any problem with the Airrave and my S5 using Wi-Fi calling.
I think I had to do that sometimes because the phone was trying to use both or maybe just to eliminate that possibility
Anyone have a solution for broken Wifi calling. I tried everything I could find including calling Sprint. Running the latest Sprint S7 update, was working before the phone updated. Really not looking forward to do a hard reset.
It's a problem with the data code on your account.Will need tech suport to fix. They are having issues with s7 not carrying code over correctly.
Thanks for the feedback, do you mean my Data plan is not correctly assigned to my phone. Ill probably have to hold the Sprint tech supports hand to get it going.
No its the actual billing codes for your account and how wifi is coded on it.
No luck, was on the phone with Sprint for almost an hour. They made a Ticket, said said I needed to take my phone to a repair center
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
cwb1231 said:
I have to tell you after the security update it reset my pattern lock and i ended up with factory reset because the Samsung website unlock feature isn't set up for the s7. Had to use Google website and my Google account to restet. Good luck
Click to expand...
Click to collapse
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
WiFi Calling
I have the same issue with my S7 with the enablement error. I have been on the phone with Sprint for over 1 hr with no help - they state it is a Samsung software issue. I went back to Best Buy where I got the phone and exchanged it but still the same problem. I took it to the Samsung reps who were there and they also were stumped. I reached out to "advanced tech Sprint support" who stated its a Samsung issue and will not be fixed until they release a patch. I reached out to Samsung and they stated they were not aware of any issues and to send the phone to their repair center - which made no sense. I see online that some have no issues doing wifi calling so it may be luck of the draw. I think that Sprint will blame Samsung who in return will say no issue. I am going to try to exchange the phone again and hope the third time works!
Did you try a hard reset?
Check wifi calling doesn't support messaging at this time..
Chetski said:
I know what you mean. Luckily I had fingerprint unlock working cause my pin unlock broke after the update. Hoping for a work around cause I got my phone setup just right. Is there a backup I can do that will restore everything exactly the way I have it now (except Wifi calling of course)? I had titanium backup years ago but it was a pain back then.
Click to expand...
Click to collapse
It only recognized my fingerprint a couple times then after power off it wouldn't. Also found out find my mobile isn't set up by Samsung for s7 yet, if ever. . I use nova launcher which allows you to save your homescreen and widget and folder setup. I use helium to back up apps and data. Restore was only really annoying not horrifically annoying. Don't forget to back up your Samsung account settings and take your sd card before you go the Google reset route. . The most help I got was the Samsung rep at best buy
Sent from my SM-T330NU using XDA-Developers mobile app
Thank you, that's a lot of great information.
I had 4 reps tell me to bring it to store for repair, did hard reset etc.... got up to advanced tech support before guy called me and said "fixed the problem, go ahead and try"and worked fine after that.
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...
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.
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Do you need to be connected to WiFi or have a certain battery level? Try charging to 100% and connecting to WiFi then manually search for the update.
What I had to do is go into the date and time and shut off auto time update and manually set it 2 days a head then mine found the update.
loffer said:
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Click to expand...
Click to collapse
Two options:
1) Borrow someone else's sim or ask At&t for another
2) Download the S10+ OTA and update via SD
Did you put the sim that came with it in? I used my old sim and had the same problem till I changed the sim card.
Sorry for the late response and thanks for the suggestions. Just returned from vacation so I will try the suggestions. Also yes I used the sim they sent me. I suspect something got messed up in the sim provisioning as I came in as a new line then ported my number in. I will try putting my wife's sim in and report back. Thanks again!
Mine wouldn't detect an update. I'm only using mine on wifi as this one is just a spare phone for now.
To get the update though I needed to put in my att dim and put the date a week in the future. That's the only way I was able to actually get it to check the server.
I'm having the same exact problem. I purchased my S10+ directly from Samsung, but it was the AT&T model. I've been stuck on the ASAT baseband with the Feb 1 Security patch since day 1. I've been on the phone/chat with AT&T for the last 3 days. Each time they've promised that they have pushed the update to my phone, and every time I check, I get the "Software is up to date" message. I just tried setting the date to next week, restarted, and checked for the update..still nothing.
The same thing happened to me with my Note 8, but I was able to get around it using ODIN. I've told AT&T that I'm not paying my bill until this is resolved (like that's gonna do anything). Anyway, I'm at the breaking point on this, and not getting anywhere fast.