Hi,
I've had my Galaxy Nexus for over 2 years now, and never had any major problems with it. However, over the past month I've been having a problem where my network connection stops working. I can't call, text or go online. I also can't receive calls or texts. When this happens, the connectivity icon still has 4 bars (or 3 or whatever).
In the past if I had network problems, I would put it in airplane mode and then turn it off, and this would reset the connection and fix it. Now, when I try to put it in airplane mode, nothing happens. The connectivity icon disappears, but the airplane icon does not appear. Then there's nothing I can do except reboot the phone. I can't even turn airplane mode off because the option is greyed out.
At first I thought I could fix the problem by resetting the phone to factory settings. That didn't work. So 2 weeks ago I installed Cyanogenmod 11, and the problem persists.
Yesterday I installed an app called "Restart Connection", but it hasn't happened since yesterday so I'm not sure if this will work or not. The problem is not regular. It can happen twice in a day, or it can not happen for 3-4 days in a row.
I'm not sure where to go from here. I've tried Googling but can't really find anything quite like this. It wouldn't be so bad if I knew when it happened, but if I don't happen to be using my phone, it can happen and then no one can call or text me until I realize that the problem is happening, so I can be without a connection for hours at a time before noticing.
Anyone have any idea what could be causing this and if there is a fix?
Thanks!
Related
I am on my second International HTC one X and both devices would lose the carrier signal quit often... I would either go to airplane mode, or turn the network off and on and it would grab it again. Sometimes it would be good for the day and other times, I would have to do it a few times....
I wanted to think it was my carrier having issues (MTS in Winnipeg MB Canada)... however, this has never happened on my many other devices. Now I wake up today and turn on the mobile data, after awhile... it does not connect, under settings it says disconnected because service is unavailable. I tried reboots, restart, airplane mode, checking apn settings.... on my last reboot, it says No signal/emergency calls only.
So now I am fearing a hardware issue (but I find it odd it happens on both my one xs).
I love this device and aside from this potentially huge issue.... I have no complaints, so I will ask here and see if you guys have any solid input.. before I contact htc!
I also popped my sim in and out, as of right now...
Thx in advance.
**update: it almost seems like putting wifi on, knocks out my carrier signal.... after an hour of doing the above things, I turned off wifi, went to airplane mode and now my signal and data is there (it makes no sense) and it is quite a hassle
The weirder part is, it seems to only be in the morning.... once I am up and running, I do not seem to have many issues through out the day, but If I put wifi on long enough... It goes to no signal/eventually....
If I do not put on wifi, it either does not drop.... or I am not noticing.
I've just begun having network problems but I'm not sure it's related to your situation. I'm in Australia on the Optus network.
It happened suddenly yesterday. Service completely cuts out for extended periods. It will occasionally come back on for a short while (long enough to download all my sms) but will then cut out again. When the signal does briefly come back in, the signal strength is decent: it's an all-or-nothing proposition.
Did you manage to resolve your situation? Would be interested to know what resolved it for you.
I've had this phone since early April when it was released here and the is the first issue I've had with it. I haven't done anything new to my phone in the past week so I'm finding this strange. I'm running Leedroid 4.0.0 but I've had that installed for weeks without issue. I'm worried it could be a hardware issue.
I'm going to try reflashing it tonight to see if it's a software issue.
I just got my Sprint GN a few weeks ago, and love using the bluetooth to connect to my car audio, but every 3rd or 4th time I get into my car I notice the bluetooth doesn't pair, so I take out my phone and look and the bluetooth icon is gray (instead of blue, indicating it has connected), I toggle the bluetooth off, and then when I try to turn the bluetooth radio back on it just sits there saying "bluetooth is turning on...". Bluetooth stops working until I reboot my phone
Does anyone have any incites into this or anyone else experiencing this?
I have the same issue. It's no solution but you can enable/disable Flightmode to get Bluetooth up and running again (but quicker then reboot).
Sent from my Galaxy Nexus using Tapatalk 2
I'll give that a try (again) next time.. I am 100% certain I had tried that, though, unfortunately.
Yeah, I tried your solution again, and it just keeps saying "bluetooth is turning on..." even after I've turned *on* airplane mode.
Need some more information to be able to help you properly >_>
Stock ROM or Custom?
Rooted/Unrooted?
Or alternatively (Because it sounds like you're running a stock Galaxy Nexus...) ave you tried unpairing, and the repairing the devices?
Hi Zach,
Completely stock & unrooted (so far)
I actually did a complete factory reset a couple days ago, and the problem has yet to resurface, so I'm crossing my fingers and hoping it's gone, but the issue was intermittent so there is no way to be completely sure it won't show up again.
If it does, I'll try your suggestion, thanks
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....
Hello! So this issue started about 2 weeks ago for me. Whenever I turn my wifi off, the phone will turn the wifi back on for 0.5-1.0 seconds then it will turn it back off. This happens nonstop. The issue persisted even when the phone was in safe mode and still continues even after 3 full factory data resets and wiping the cache partition 3 times as well. I did this through recovery mode. Nothing changed. When this is happening, it seems to drain my battery significantly. The only fix I have found for it has been to leave my wifi on all the time, even when I am not connected to or near a wifi hotspot. The issue also does not happen when the phone is in airplane mode. Also, I did not receive any software updates around the time this issue started happening. I have tried Googling and contacting Samsung and could not come up with a fix.
Is anyone else having or had this issue? If so, did you find any fix? Thanks!
If this thread needs to be moved to the help/troubleshooting section, please tell me how to do that, or do that yourself if you would like mods. This is my first time starting a thread so I am sorry if I put it in the wrong place.
Possible Fix
My Note 7 and S7 Edge were doing the same. I fixed it by disabling "Wifi scanning even while Wifi is turned off" in location settings.
This happens at least 4 times a day, it's annoying, I have to switch to airplane mode and back again to get it to reconnect.
I also get this sometimes . When I look at the wifi access point on the phone, it says that its down to poor internet quality .It usually corrects itself in approx 10 minutes with no action taken on my part.
Do you have WiFi set to turn off when the phone is asleep? If so, try setting it so WiFi stays on during sleep and see if that helps.
I got the same problem since I rooted
Been trying to figure out if its a VENDOR Firmware problem or what. I do know that every developer says its a bug with the s9 when rooting. I've personally watch the live log on TWRP when flashing and seen where it mounts the VENDOR Firmware and then unmounted at the end. So it could possibly be a problem between TWRP and the s9 ROMs idk know exactly yet but I'm looking for a solution also. Keep your head and keep searching also then reply back here when you find something. I'll do the same. Good luck.
Its still happening sometimes its fine a for a couple of days then it starts acting up, my girlfriends S9 does the same so maybe it's something to do with Virgin Routers.