Vodafone UK sent out the upgrade to Nougat and I was 1st to jump on it. 1 thing I noticed was wifi calling that used to work great on marshmallow is now broken.
It used to switch over if my signal dropped, mainly noticed in supermarkets and Ikea (metal walls) then switch back once I had a couple of bar signal.
Since the upgrade it tends to come on after a while and stay there, I did assume it was due to upgrading without wiping so once I had the time I backed up and reset the phone from recovery, followed the hours adding all my accounts back and sent the text to Vodafone to enable it again, sure enough the option popped up in call settings and I enabled it.
Now I get 4 to 5 bars at home so 80% signal and the bloody thing keeps coming back and staying on, if I reboot the phone it will go again for a while then come back. I can park next to the bloody transmitter with a full signal and it stays on!
Anyone else got this or know of a fix besides turning wifi calling off?
Thanks.
Related
I'm having a rather specific and odd problem with my captivate(s), three of them to be exact. First I bought the phone, upgrading from an Iphone 3g, and the first day it was great, the second day, in the evening, I noticed that it started this strange rebooting loop. The phone doesn't seem to power off because I don't see the Galaxy S symbol it just merely goes black then comes back and searches for the network, finds it, then a few minutes later goes black again, returns, search for the network, and so on. It keeps doing that over and over again. So I tried a factory reset the next morning just to make sure it wasn't a problem with any apps installed. The same rebooting loop happened. So I called a rep and dropped by the ATT store and they said it might be the sim card, which was very very old (still said cingular) so we swapped it. Same problem the next day. Okay so I went and I replaced the whole phone. The second day with Captivate #2, this rebooting loop occurred again. The reps told me that I might have gotten two bad ones and to exchange it again, so I did. And yet again I have the same problem. So here are some quick facts about the problem that I have learned. Total time span has been about 3 weeks.
-The most important thing to know about this issue is that the only thing that prevents the phone from going into this rebooting loop is if I enable flight mode, no network connectivity. I believe wi-fi is okay but whenever I disconnect from ATT's network it stops rebooting.
-Occurs more frequently at night/evening (only happened once in the morning)
-Is not affected by signal strength, full bars, low bars.
-Is not affected by installed apps (Had done factory resets and with my third captivate all I did was put the sim card in and put it in my pocket)
-Is not affected by battery status, low or full
-Doesn't seem to matter if I have a lot of things running or nothing running, the loop starts when I'm browsing, texting, in a call, or just locked in my pocket.
-Does not seem to be affected by charging source (wall, car, laptop, ps3/xbox)
Another thing to note is that I had an Iphone 3G with an unlimited data plan before this. The Captivate upgrade was done on another line on my family plan then given to me with a 2gb data plan. After talking to multiple reps over the phone, they said they had the wrong IMEI number (I have no idea what that means) but that leads me to wonder what else is wrong and is it a problem with the Captivates or ATT itself?
I really need some feedback because I'm about to just give up on this phone, which is heartbreaking because I fell in love it. My 30 days is approaching and if I am indeed returning it, it'll have to be very soon. What do you guys think?
I live in Manhattan, so my day consists of going underground for subway, and then back out at least 4 times per day. I have noticed several times that my radio never RE-grabs a signal when coming above ground it just sits with the bars and an X signifying no signal, in broad daylight...until i reboot the phone and it then promptly grabs signal. I have a buddy with a NS and he noticed this too...we also noticed it happens mostly when we are listening to something when emerging back above ground. Not sure if that has anything to do with it, or if it isjust cooincidence...however, has anyone else noticed their NS radio not grabbing a signal when back in range??? It is SO annoying to be walking around for 10-15min after coming above ground, to notice you have been cut off the whole time.
just instal the airplane mode on/off toggle
and hit it when you are back out on the surface
some times it's slow for the machine to grab signal
yes, i have noticed
like when i go into the basement, or server room, or other places with NO signal
and go back out to a place that I Know there is signal, yet it still in X mode
so, i just swap on/off airplane mode, and it works right away
mcosmi said:
I live in Manhattan, so my day consists of going underground for subway, and then back out at least 4 times per day. I have noticed several times that my radio never RE-grabs a signal when coming above ground it just sits with the bars and an X signifying no signal, in broad daylight...until i reboot the phone and it then promptly grabs signal. I have a buddy with a NS and he noticed this too...we also noticed it happens mostly when we are listening to something when emerging back above ground. Not sure if that has anything to do with it, or if it isjust cooincidence...however, has anyone else noticed their NS radio not grabbing a signal when back in range??? It is SO annoying to be walking around for 10-15min after coming above ground, to notice you have been cut off the whole time.
Click to expand...
Click to collapse
I'm also a metro north commuter and the same thing happens to me randomly as well. I can go days without it occurring once, however sometimes it'll happen twice in the same day. Attempting to cycle Airplane Mode just locks up the device as well, so rebooting is the only option to restore network connectivity.
Noticed this as well when I'm in and out of subway stations. It hasn't been happening recently but sometimes playing around with the settings in the *#*#4636*#*# menu might help, like selecting GSM PRL or WCDMA preferred.
Anyway, I had the same problem with my Vibrant... never had the problem with my Nexus One or MyTouch 4G. Maybe HTC's hook onto networks better?
mcosmi said:
I live in Manhattan, so my day consists of going underground for subway, and then back out at least 4 times per day. I have noticed several times that my radio never RE-grabs a signal when coming above ground it just sits with the bars and an X signifying no signal, in broad daylight...until i reboot the phone and it then promptly grabs signal. I have a buddy with a NS and he noticed this too...we also noticed it happens mostly when we are listening to something when emerging back above ground. Not sure if that has anything to do with it, or if it isjust cooincidence...however, has anyone else noticed their NS radio not grabbing a signal when back in range??? It is SO annoying to be walking around for 10-15min after coming above ground, to notice you have been cut off the whole time.
Click to expand...
Click to collapse
I normally loose signal completely when I am in the underground parking lot of my condo building. But as soon as I am outside it connects almost immediately.
brianbrain said:
I'm also a metro north commuter and the same thing happens to me randomly as well. I can go days without it occurring once, however sometimes it'll happen twice in the same day. Attempting to cycle Airplane Mode just locks up the device as well, so rebooting is the only option to restore network connectivity.
Click to expand...
Click to collapse
I've got the exact same problem, not sure how to resolve it. Really wish they would push out an update and fix these annoying issues.
I've set my phone to WCDMA Only ( since and on boot up it doesnt connect to a network ) & WCDMA Perferred doesn't seem to want to stick.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en
i have the same problem
Same problem with my Nexus S. Toggling airplane mode don't help. I have to power off/on my Nexus S then I get the signal again.
I am currently running Ninja-0706, radio 26.06.06.30_M.
Intermittantly, my phone will drop out of H and start cycling through all the connections, edge, gsm, 3G etc. After cycling through, it will go to no connection at all where you see "no service" on the screen. And it will stay like that for several minutes, no matter where I am standing in my apartment, or even if i walk outside. Then all of a sudden, it will pick up H, full bars and it will stay like that.
So far, this issue has only happened a couple of times, within the past couple of weeks, and at my apartment. I have full wiped and flashed different roms, and reflashed the radio after the first time this happened, so this issue cannot be blamed on current said rom. This has led me to suspect that maybe there is an issue with the tower in my area. Twice I have called AT&T now about this issue. Both times they claim there have been no outages or issues with the towers in my area. They also claim that the closest tower to me is about 1 mile away, so there shouldn't be issues as such with a tower so close. I don't know anyone in my complex who is on AT&T to see if they are experiencing the same issue. So AT&T seems to think there might be an issue with the phone and i might need to do a warranty exchange. Any ideas before I flash back to stock and exchange it out?
While mine doesn't go that far, it'll cycle between H and 3G for no apparent reason.
Mine does weird **** sometimes, too, on Tue 04_11_M2 radio.
Just today I was sitting around browsing via WiFi, and bam, no signal. Most if the time it'll kick back in after a sec or two, but it stays like that until I intervene by toggling airplane mode, then, it'll be back to 3-4 bars or whatever.
Second time its happened over the last month, so no biggy.
In my house I get lots of signal variations overall, which I guess should be expected.
Well, my phone has done it twice since OP. I just flashed back to stock and downgraded to s-on. I'm going to see about an insurance claim.
Update: Just got off the phone with AT&T. They said that this issue would need to be handled by the warranty dept. So got back on the phone with tech support and they suggested that I go into an AT&T store and have the sim card replaced before they replace the phone, as the sim card itself might be causing this issue. It seems plausible because the sim card is needed for a connection to the network.
I searched and did not see anyone else experiencing this issue. I have a Black 32 GB stock rooted. It worked fantastic for about 2 weeks and then all of a sudden I noticed the following:
Day 1: No SMS received. I was on WIFI and had network signal in the notification bar but did not receive SMS that were sent to me.
Day 2: No Cellular Signal. I looked at the APN and it had disappeared. I attempted to add it again and reboot the phone and it wouldn't add. The phone began rebooting on its own and continuing with a bootloop after running for about 10 seconds it would reboot again. It did this throughout the day. I called Google and they had me do some soft and hard resets. After the soft reset the phone would connect right after startup then disconnect after 2 seconds and reboot itself. I hard reset the phone and relocked the bootloader and reinstalled factory recovery and it is still doing it.
Google has given me authorization for an exchange but I was just wondering if anyone had any ideas because I'd rather not be without a phone for 2 weeks.
BTW I am on Straight Talk
I had a similar issue
I had a similar issue. After a month of functioning normally, my Nexus(rooted using CFroot, stock ROM, T-Mobile) lost the ability to get reception. First, it showed network signal, but cell access was not functional. A few hours later, bars dropped to zero, and it seemed like I could only get reception in the strongest signal areas. I would get signal sporadically when driving, but never when I was stationary. The phone never had problems with rebooting though.
After spending a day trying to fix it, factory reset, relock, flashing a factory image, I called Google, and they warranteed the phone.
nebrando said:
I searched and did not see anyone else experiencing this issue. I have a Black 32 GB stock rooted. It worked fantastic for about 2 weeks and then all of a sudden I noticed the following:
Day 1: No SMS received. I was on WIFI and had network signal in the notification bar but did not receive SMS that were sent to me.
Day 2: No Cellular Signal. I looked at the APN and it had disappeared. I attempted to add it again and reboot the phone and it wouldn't add. The phone began rebooting on its own and continuing with a bootloop after running for about 10 seconds it would reboot again. It did this throughout the day. I called Google and they had me do some soft and hard resets. After the soft reset the phone would connect right after startup then disconnect after 2 seconds and reboot itself. I hard reset the phone and relocked the bootloader and reinstalled factory recovery and it is still doing it.
Google has given me authorization for an exchange but I was just wondering if anyone had any ideas because I'd rather not be without a phone for 2 weeks.
BTW I am on Straight Talk
Click to expand...
Click to collapse
flmz said:
I had a similar issue. After a month of functioning normally, my Nexus(rooted using CFroot, stock ROM, T-Mobile) lost the ability to get reception. First, it showed network signal, but cell access was not functional. A few hours later, bars dropped to zero, and it seemed like I could only get reception in the strongest signal areas. I would get signal sporadically when driving, but never when I was stationary. The phone never had problems with rebooting though.
After spending a day trying to fix it, factory reset, relock, flashing a factory image, I called Google, and they warranteed the phone.
Click to expand...
Click to collapse
It just seems so much like a software issue as opposed to hardware that it surprises me they are willing to warranty it... but I guess I'm not the expert.
How long did it take you to get your replacement phone?
nebrando said:
It just seems so much like a software issue as opposed to hardware that it surprises me they are willing to warranty it... but I guess I'm not the expert.
How long did it take you to get your replacement phone?
Click to expand...
Click to collapse
I got a replacement phone pretty quickly. The phone shipped the day after I ordered the replacement, but YMMV.
Why do you think it was a software issue? The problem persisted after I switch back to a factory image. The replacement phone, running the same software does not have the same issue.
flmz said:
I got a replacement phone pretty quickly. The phone shipped the day after I ordered the replacement, but YMMV.
Why do you think it was a software issue? The problem persisted after I switch back to a factory image. The replacement phone, running the same software does not have the same issue.
Click to expand...
Click to collapse
That makes sense that it was a hardware issue. I guess it could be a faulty radio or something. I'm glad to hear you got your device shipped so soon. Did you end up having to pay shipping?
I ran a nexus 5 for about 4 days and went through two of them both having issues holding a signal. Both phones would start with LTE and then drop to 2g go to 3g and then 4g back to no bars and then 2g and 3g. I was stock all the way and I wish the nexus 5 worked better. It could be a software issue as when I took the OTA to 4.4.2 it became worse. All the areas I was in while this happened were areas that were supposed to be strong for 4g and LTE.
That said I I need a phone that is a bit more reliable even though I'm on T-Mobile. I switched to the LG G2. It has a better antennae and doesn't keep bouncing between modes when in various areas.
Hello,
I'm asking for some help to diagnose my call problems on UMTS.
First of all, three things happened recently, and let's assume that they happened roughly at the same time:
I dropped my Nexus 5 on concrete shattering the screen completely;
Google released Lollipop which some people believe has problems with 3G and LTE;
I'm using a rather old SIM card manually cut to fit micro-SIM dimensions.
About two days after receiving my Nexus 5 back from guys servicing it (new LCD screen) I had a telephone conversation that was disconnecting once every minute or two. There was no problem recalling though. The same day later I noticed that dialer app says "Emergency calls only" which was pretty weird. I was on Cyanogenmod 11, some recent nightly back then.
My first guess - revert to earlier nightly via TWRP. It didn't help - I was still on emergency calls only and nobody was able to call me. However, I could browse Internet without any problems on 3G.
Second guess - clean flash stock 5.0.1. It didn't help too, however calling went back on for some time (several minutes) before breaking back to "Emergency calls only".
Third guess - buy a starter SIM and check if it works. It did at first but stopped after an hour or so.
Fourth guess - bring the phone back to guys servicing the LCD to check antennas. I've left it for two days. It was opened and antennas checked. Everything was fine, not even a bent flex.
For all this time when on 3G/LTE data transmission worked flawlessly. I could download Google Maps, browse the Internet, whatever. It's just the very basic phone function that acts weird - as if I wasn't registered to a network. Everything seems to work fine on 2G, except for very rare disconnects (once per two, or three days).
So, considering it's pretty weird I'm seeking for help - could it be possible that after hitting concrete something broke down on the motherboard that results in such weird behavior? Or is, perhaps, my retro-SIM dying? Any ideas? Maybe flashing a well-tested radio ROM? Diagnostic apps?