I'm running Nougat but I've not been happy with the battery life. I'd like to odin back down to the last MM update. I shouldn't have a problem because it uses version 4 of the BL. When I check TMO's support site for the S7 they call the Nougat update "manditory". So my question is has anyone been able to stay on MM unrooted and not been forced to take the update?
I have a G930U always on wifi but no sim. It downloaded the update a while back and does push it about once a day, but I keep saying later and it goes away for a day.. I also have a S7 Edge which went to Nougat, I have not seen battery life issue per-say, but it does seem "clunkier" seems even more "stock" features are hidden by default, and most frustrating is I now have the wifi issue: "Wifi Connected, No Internet" - "Wifi Calling enabled" .. huh? It seems to sometimes work on wifi data and sometimes "choose" mobile, I've used more mobile data than ever because of this and it worries me that I may have missed calls..
Related
So recently I've been having a lot of issues with my cell reception. Randomly during the day I would completely lose my reception. However the icon in the status bar will show I got a full connection. Mobile data works. But I will be unable to receive / make calls or text messages. A reboot will fix this. I've had this issue ever since an ota update from sultanrom. I've since tried flashing the stock ROM back but it happens on there as well. I'm currently on the latest sultan mm version. But this used to happen on his lollipop version as well It mostly seems to happen when charging my phone. I've tried different firmwares and modems but the issue is still there. This is a big problem because I've gone for 10+ hours several times without any cell reception thinking all was fine because the status bar shows a full connection. Has anyone else had this issue? I really need to get this sorted as it makes my phone unable to do the most basic things a phone should be doing.
I was curious if anyone else experienced or has familiarity with this issue. I've been dealing with this since I got the phone almost a year ago. Sometimes when my phone has been idling and I return to check something, the data connection will be unusable. The 3G icon will be visible but internet unavailable (4G works fine, but I prefer to have my phone set to 3G only). It's possible to wait 30-60 seconds for the connection to reset itself, or under settings, switching "Cellular data" or Airplane mode also restores it. Aside from that, the connection is mostly reliable & I don't have any usability issues once data has restored.
I've always ran CM & LOS on this phone so I haven't tried using a stock ROM (solution suggested in an older thread... Mobile data cutting out). I've also flashed the latest Lollipop Radio Firmware (fsg & modem). Thanks for any help.
Edit: I think this may have had something to do with visual voicemail being enabled. I've since switched to AT&T where VVM hasn't worked at all (they suggest using their app) and the problem has gone away.
Hello,
I have a carrier unlocked Pixel 2 walleye that is rooted (magisk, no custom recovery) and on Verizon
android version 8.1.0
build #OPM1.171019.021
when I try to activate wifi calling, i get the spinning circle for a long time, and then it finally says "unable to activate wi-fi calling. please try again later"
I have HD voice activated on my verizon wireless account.
I tried the VoEnabler module in Magisk
Wifi calling is turned on in the phone info screen (*#*#4636#*#*)
The only thing i guess i haven't tried is installing a Verizon ROM instead of the stock Google ROM.
Before I went that route, I wanted to check here and see if anyone else was able to get it to work for them.
Thanks in advance.
ok so i had this issue twice on the same phone and i am rooted as well. i think the only way to get it to work is to disable root, activate wifi calling, then reactivate root.
I have enabled this feature while rooted on 2 different PIxel 2's.
This sounds silly but turn off wifi and try to activate it. I've been unable to input my address during the activation process multiple times unless I am on cellular.
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I don't think your problem is related to root unless it's a Magisk module of some kind that's the problem. I'm on Verizon, rooted with Magisk. I haven't had wireless calling turned on but after seeing your post I thought I'd check and see if it works on mine. It connected without any problems for me.
Did you ever figure this out?
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I'm having a similar issue, except that I can enable wifi calling but always get the "Turn off airplane mode or connect to a wireless network" message when attempting to place a wifi call. Everything with regard to wifi calling is set up correctly. I thought I had this narrowed down to Oreo version and patch level, but I honestly can't come up with a repeatable scenario that breaks it. About all I can say for sure is it seems like when I flash back to bone stock, OPM1.171019.021, wifi calling works as expected. However, it seems to break after a while, even without applying any updates. My gut says it's related to root, but I've also seen it work with root. I also have a suspicion it has something to do with the type of authentication on the wifi network, as the first time I ever saw wifi calling work was when I connected to an open SSID. The problem is, right after that, it worked fine on a WPA2 network on which it never worked before. This is on Verizon with a Pixel 2 from the Google Store. I have a hard time believing it's a Verizon issue, though. It's more like the phone does a check for wifi connectivity and returns "false" for some reason.
*** I should add all my testing has been done by turning on airplane mode (thus disabling LTE/3G) and then enabling wifi. My office at work has horrendous cell coverage, but I haven't gotten it down to zero bars without airplane mode to see if it works then.
Hi,
I have a g930p running g930u Nougat firmware. I did an OTA update to Oreo and was not able to connect to my network after.
I'm in Canada and on Public Mobile which is owned by Telus.
I can see Telus, Bell, Rogers, and Freedom when I do a manual network search, but cannot connect to any of them.
I did some research, and I'm wondering if there are some issues with MVNO's.
My IMEI is present, so I don't think there is an issue there.
I was able to use Odin to downgrade back to Nougat. Everything works fine on Nougat.
I tried manually flashing the latest g930u oreo firmware after, and no luck. A factory reset did not help either.
Any ideas?
Thanks!
Same Issue here
Hello,
I seem to have a very similar issue.
Ever since the most recent update (to Oreo 8.0.0) my Samsung Galaxy S7 will not connect to mobile networks. The network symbol shows full four bars most of the time (sometimes the crossed out circle), however never indicators for mobile internet. I don't receive texts or whatsapp messages, neither can I send them, the browser says I'm offline. I can't be called and when trying to make calls, after a split second I get a prompt "Not registered on network" and the call ends.
Internet usage works just fine when using Wifi.
Also, the issue only occurs on default network settings: When I go to settings->connections->mobile networks->network mode and select "2G only", the phone functions as I would expect it to do. All other modes don't work.
Things I've tried without any form of success:
Flight mode on/off
Several reboots
Wiping the cache
Manually searching for network operators (keeps on scanning forever)
Resetting network settings
Resetting my phone to factory settings
Unfortunately I can't cross check my SIM-card with other phones or other SIM cards on my device. Since I've been using both for almost 2 years now, however, I don't think those are the issue.
Device: Samsung Galaxy S7 32GB
Android Version: 8.0.0
Product Code: SM-G930FZKADBT
Baseband version: G930FXXU2ERGC
Build number: R16NW.G930FXXU2ERGE
Network Provider: Mobilcom debitel (Via D2 network, Germany)
I really hope somebody has an idea for a solution, this unnecessary issue renders the phone mostly unusable :/
Hi
A UK user here, I have been experiencing some of the same issues that you have both mentioned. For me however periodically my phone will stop recieving network signal from my phone operator '3' and have completely no signal. This has been happening for a few months now and has happened since the last major update. In attempting to solve the issue, I often reset my phone multiple times to no avail and I simply have to wait until the phone starts to recieve signal again! Very frustrating!
I am not using any type of custom OS currently (or ever previously) and that was my main motivation to join this site, to jailbreak my phone and see if I can overcome these issues through custom fireware or alternatively installing older firmware where this problem did not exist.
The problem is widespread, a simple google of the issue or a visit to the Samsumg forum and you'll find plenty of users reporting the same problem, however Samsung seems to be doing nothing about it. Honestly, I am disgusted! I paid a lot of this phone on its release two years ago and I have simply been forgetten about and no one seems to care at Samsung to provide a solution or any information at all.
Best,
I recently acquired a Permanently Unlocked US T-Mobile Galaxy s7 SM-G930T. Since I have Verizon, I flashed it to the latest Verizon Firmware SM-G930V from sammobile using the latest Odin. Everything went perfect.
The only problem is that the wifi will not stay connected.
It will connect for a few minutes at a time, and then, despite it saying it is still connected to wifi, videos will suddenly not load, apps will not open. I run a speed test and then it will show the little exclamation mark on my wifi signal, only then showing that wifi is not connect or having problems. It's very tedious as I go based off the wifi signal to and since it says it's connected i am missing important notifications despite my mobile data being connected. I have unlimited data with my carrier so i could simply stay connected to mobile data at all times, but i would like to have my wifi working again. Does anybody know what may be causing this problem.
I tried flashing it back to T-Mobile. and once again everything works perfect. except for the wifi. So i believe it may have to do with the firmware, or maybe i need another file or files that i still need to install? I have been researching it for a week and i just can not figure out a solution.
I tried resetting my router, nothing.
Different older firmwares for Verizon from Sammobile, nothing.
Resetting Cache in recovery mode, nothing.
Unchecking Smart switch (function for it to switch between mobile and wifi automatically), nothing.
Unchecked Wifi and bluetooth scanning, nothing.
Can somebody please help?
Just asking, what were the bootloader versions of the T-Mobile and Verizon ROM's you went back and forth with? *Bootloader version can be found in baseband number i.e SM-930TUVS4CRL1, The 4 is the BL.